From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: 766@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
Peter_Dyballa@Freenet.DE
Subject: bug#766: 23.0.60; interesting warning during compilation
Date: Sat, 23 Aug 2008 23:50:18 +0300 [thread overview]
Message-ID: <uabf33185.fsf@gnu.org> (raw)
In-Reply-To: <jezln3cxd8.fsf@sykes.suse.de>
> From: Andreas Schwab <schwab@suse.de>
> Cc: 766@emacsbugs.donarmstrong.com, Peter_Dyballa@Freenet.DE,
> bug-gnu-emacs@gnu.org
> Date: Sat, 23 Aug 2008 22:03:31 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I meant the warning about shifting by too many bits. 31+1 = 32, and
> > even a compiler can realize that.
>
> That's not how the shift operator is defined.
Andreas, it's late and I'm tired. Could you please answer my
question, which is: what is the danger, if any, that GCC in some
future version will produce the same warning for the code you
suggested?
Thanks in advance.
next prev parent reply other threads:[~2008-08-23 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k5e2uvl4.fsf@cyd.mit.edu>
2008-08-23 9:00 ` bug#766: 23.0.60; interesting warning during compilation Peter Dyballa
2008-08-23 14:10 ` Eli Zaretskii
2008-08-23 14:58 ` Peter Dyballa
2008-08-23 17:34 ` Eli Zaretskii
2008-08-23 22:23 ` Peter Dyballa
2008-08-24 3:13 ` Eli Zaretskii
2008-08-24 7:27 ` Peter Dyballa
2008-08-24 18:12 ` Eli Zaretskii
2008-08-23 17:33 ` Andreas Schwab
2008-08-23 18:18 ` Eli Zaretskii
2008-08-23 18:56 ` Andreas Schwab
2008-08-23 19:06 ` Eli Zaretskii
2008-08-23 20:03 ` Andreas Schwab
2008-08-23 20:50 ` Eli Zaretskii [this message]
2008-08-23 23:12 ` Andreas Schwab
2008-08-24 3:14 ` Eli Zaretskii
2008-09-03 18:47 ` Stefan Monnier
2008-08-27 19:10 ` bug#766: marked as done (23.0.60; interesting warning during compilation) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uabf33185.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=766@emacsbugs.donarmstrong.com \
--cc=Peter_Dyballa@Freenet.DE \
--cc=bug-gnu-emacs@gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.