unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 22:06:12 +0300	[thread overview]
Message-ID: <ud4jz361n.fsf@gnu.org> (raw)
In-Reply-To: <je7ia7ef15.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 20:56:38 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Andreas Schwab <schwab@suse.de>
> >> EMACS_INT high_ino = s.st_ino >> 31 >> 1;
> >
> > Thanks.  Can we be reasonably sure that GCC will not become smart
> > enough some day to flag this as well?
> 
> What do you mean with "smart enough"?

Maybe that was a polite way of saying "silly enough".

> There is nothing to flag here.

I meant the warning about shifting by too many bits.  31+1 = 32, and
even a compiler can realize that.

Please don't get me wrong: I will gladly make the change as you
suggested, I just don't want us to bump into this again a few GCC
upgrades down the road.






  reply	other threads:[~2008-08-23 19:06 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 [this message]
2008-08-23 20:03             ` Andreas Schwab
2008-08-23 20:50               ` Eli Zaretskii
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ud4jz361n.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).