unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 766@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#766: 23.0.60; interesting warning during compilation
Date: Sun, 24 Aug 2008 21:12:02 +0300	[thread overview]
Message-ID: <u1w0e2sgd.fsf@gnu.org> (raw)
In-Reply-To: <6B6799DA-F80E-4B4F-A102-F9EBDA5CDA9F@Freenet.DE>

> Cc: 766@emacsbugs.donarmstrong.com,
>  bug-gnu-emacs@gnu.org
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> Date: Sun, 24 Aug 2008 09:27:16 +0200
> 
> 
> Am 24.08.2008 um 05:13 schrieb Eli Zaretskii:
> 
> > If you mean with sizeof, then the problem is that sizeof is not a
> > preprocessing-time operator, so it cannot prevent the compiler from
> > seeing the offending code.
> 
> You mean
> 
> 	if (sizeof (s.st_ino) > 4)
> 
> introducing the shift operation will fail to keep the compiler from  
> emitting the warning?

Yes, it will fail.  Please try compiling this toy program on a 32-bit
machine, and you will see the same warning.

    int foo (int a)
    {
      if (sizeof (a) > 4)
	return a >> 32;
      else
	return 0;
    }

> Anyway, I think Andreas Schwab's proposition to split the one wide  
> shift into two shorter ones is better.

I agree, I just wanted to be sure that this won't bring the same
warning back at some future time.






  reply	other threads:[~2008-08-24 18:12 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 [this message]
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
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=u1w0e2sgd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=766@emacsbugs.donarmstrong.com \
    --cc=Peter_Dyballa@Freenet.DE \
    --cc=bug-gnu-emacs@gnu.org \
    /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).