This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Char shifts promoted to int. Why?

From: Robert Dewar <dewar at adacore dot com>
To: Chris Lattner <clattner at apple dot com>
Cc: Paul Schlie <schlie at comcast dot net>, Paul Brook <paul at codesourcery dot com>, gcc at gcc dot gnu dot org
Date: Mon, 18 Dec 2006 12:24:14 -0500
Subject: Re: Char shifts promoted to int. Why?
References: <C1ABD69F.F4DA%schlie@comcast.net> <AD0EDC2B-2CDC-4103-AC6D-060DAA96F550@apple.com>

Chris Lattner wrote:

Sorry, but you're incorrect. While it may be "logical" that shifting a value left more bits than its size will give you zero, this is not what C specifies.


I am puzzled, what exactly *does* C specify in this case? I reread
the thread, but it's not clear what the requirement of the standard
here is (as opposed to what programmers might or might not expect,
or what hardware does or does not do).

Follow-Ups:
- Re: Char shifts promoted to int. Why?
  - From: Chris Lattner
- Re: Char shifts promoted to int. Why?
  - From: Richard Kenner

References:
- Re: Char shifts promoted to int. Why?
  - From: Paul Schlie
- Re: Char shifts promoted to int. Why?
  - From: Chris Lattner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]