public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Michael Marks <Michael.Marks@internetmachines.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c/10226: unsigned short promotion with bitwise inversion
Date: Thu, 27 Mar 2003 00:16:00 -0000	[thread overview]
Message-ID: <20030326231601.1327.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10226; it has been noted by GNATS.

From: Michael Marks <Michael.Marks@internetmachines.com>
To: 'Falk Hueffner' <falk.hueffner@student.uni-tuebingen.de>, 
	Glen Nakamura <glen@imodulo.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: RE: c/10226: unsigned short promotion with bitwise inversion
Date: Wed, 26 Mar 2003 15:10:54 -0800

 This message is in MIME format. Since your mail reader does not understand
 this format, some or all of this message may not be legible.
 
 ------_=_NextPart_001_01C2F3EC.F3696FC0
 Content-Type: text/plain;
 	charset="iso-8859-1"
 
 Guys,
 How about...
 warning: comparison will will promote to ~(unsigned) which will zero extend
 before ~ operation
 
 -----Original Message-----
 From: Falk Hueffner [mailto:falk.hueffner@student.uni-tuebingen.de]
 Sent: Wednesday, March 26, 2003 2:54 PM
 To: Glen Nakamura
 Cc: Michael Marks; gcc-gnats@gcc.gnu.org
 Subject: Re: c/10226: unsigned short promotion with bitwise inversion
 
 
 Glen Nakamura <glen@imodulo.com> writes:
 
 > On Wed, Mar 26, 2003 at 11:19:58PM +0100, Falk Hueffner wrote:
 > > Glen Nakamura <glen@imodulo.com> writes:
 > > > How about one of these:
 > > > warning: comparison of promoted ~unsigned with unsigned is always
 false
 > > > warning: comparison of ~(promoted unsigned) with unsigned is always
 false
 > > 
 > > Yes, that makes it even clearer. I'd prefer the second variant.  (BTW,
 > > funny, the optimizer doesn't seem to realize it's always false...)
 > 
 > It does on my system (GCC 3.3):
 
 Well, yeah, it's simply constant folding there. What I meant is that
 gcc doesn't optimize
 
 int f(unsigned short a, unsigned short b) { return b == ~a; }
 
 to
 
 int f(unsigned short a, unsigned short b) { return 0; }
 
 -- 
 	Falk
 
 ------_=_NextPart_001_01C2F3EC.F3696FC0
 Content-Type: text/html;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
 <HTML>
 <HEAD>
 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
 charset=3Diso-8859-1">
 <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2653.12">
 <TITLE>RE: c/10226: unsigned short promotion with bitwise =
 inversion</TITLE>
 </HEAD>
 <BODY>
 
 <P><FONT SIZE=3D2>Guys,</FONT>
 <BR><FONT SIZE=3D2>How about...</FONT>
 <BR><FONT SIZE=3D2>warning: comparison will will promote to ~(unsigned) =
 which will zero extend before ~ operation</FONT>
 </P>
 
 <P><FONT SIZE=3D2>-----Original Message-----</FONT>
 <BR><FONT SIZE=3D2>From: Falk Hueffner [<A =
 HREF=3D"mailto:falk.hueffner@student.uni-tuebingen.de">mailto:falk.hueff=
 ner@student.uni-tuebingen.de</A>]</FONT>
 <BR><FONT SIZE=3D2>Sent: Wednesday, March 26, 2003 2:54 PM</FONT>
 <BR><FONT SIZE=3D2>To: Glen Nakamura</FONT>
 <BR><FONT SIZE=3D2>Cc: Michael Marks; gcc-gnats@gcc.gnu.org</FONT>
 <BR><FONT SIZE=3D2>Subject: Re: c/10226: unsigned short promotion with =
 bitwise inversion</FONT>
 </P>
 <BR>
 
 <P><FONT SIZE=3D2>Glen Nakamura &lt;glen@imodulo.com&gt; writes:</FONT>
 </P>
 
 <P><FONT SIZE=3D2>&gt; On Wed, Mar 26, 2003 at 11:19:58PM +0100, Falk =
 Hueffner wrote:</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; Glen Nakamura &lt;glen@imodulo.com&gt; =
 writes:</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; &gt; How about one of these:</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; &gt; warning: comparison of promoted =
 ~unsigned with unsigned is always false</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; &gt; warning: comparison of ~(promoted =
 unsigned) with unsigned is always false</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; </FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; Yes, that makes it even clearer. I'd =
 prefer the second variant.&nbsp; (BTW,</FONT>
 <BR><FONT SIZE=3D2>&gt; &gt; funny, the optimizer doesn't seem to =
 realize it's always false...)</FONT>
 <BR><FONT SIZE=3D2>&gt; </FONT>
 <BR><FONT SIZE=3D2>&gt; It does on my system (GCC 3.3):</FONT>
 </P>
 
 <P><FONT SIZE=3D2>Well, yeah, it's simply constant folding there. What =
 I meant is that</FONT>
 <BR><FONT SIZE=3D2>gcc doesn't optimize</FONT>
 </P>
 
 <P><FONT SIZE=3D2>int f(unsigned short a, unsigned short b) { return b =
 =3D=3D ~a; }</FONT>
 </P>
 
 <P><FONT SIZE=3D2>to</FONT>
 </P>
 
 <P><FONT SIZE=3D2>int f(unsigned short a, unsigned short b) { return 0; =
 }</FONT>
 </P>
 
 <P><FONT SIZE=3D2>-- </FONT>
 <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
 SIZE=3D2>Falk</FONT>
 </P>
 
 </BODY>
 </HTML>
 ------_=_NextPart_001_01C2F3EC.F3696FC0--


             reply	other threads:[~2003-03-26 23:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  0:16 Michael Marks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 23:06 Falk Hueffner
2003-03-26 22:36 Glen Nakamura
2003-03-26 22:26 Falk Hueffner
2003-03-26 22:26 Glen Nakamura
2003-03-26 22:06 Michael Marks
2003-03-26 21:56 Glen Nakamura
2003-03-26 21:56 Falk Hueffner
2003-03-26 21:16 Michael Marks
2003-03-26 21:16 ebotcazou
2003-03-26 20:36 Glen Nakamura
2003-03-26 19:56 Michael Marks
2003-03-26 18:26 Falk Hueffner
2003-03-26 18:16 mmarks

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=20030326231601.1327.qmail@sources.redhat.com \
    --to=michael.marks@internetmachines.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.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.
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).