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: Wed, 26 Mar 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030326215601.15620.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: 'Glen Nakamura' <glen@imodulo.com>, Falk Hueffner
	 <falk.hueffner@student.uni-tuebingen.de>
Cc: Michael Marks <Michael.Marks@internetmachines.com>, 
	gcc-gnats@gcc.gnu.org
Subject: RE: c/10226: unsigned short promotion with bitwise inversion
Date: Wed, 26 Mar 2003 13:50:29 -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_01C2F3E1.B7E36740
 Content-Type: text/plain;
 	charset="iso-8859-1"
 
 Either is far clearer than the original.  
 I like the second one better.
 
 Just one other comment, are both promoted, and are both unsigned after the
 promotion.
 I thought they are promoted to int. As per you earlier...
 
 The ~ operator is subject to integer promotion,
 so with the implicit conversions the expression becomes:
   if ((int) B == ~((int) A))
 which is indeed false in the example above.
 
 But like I said earlier, either message below is far clearer.
 
 Thanks,
 Michael.
 
 -----Original Message-----
 From: Glen Nakamura [mailto:glen@imodulo.com]
 Sent: Wednesday, March 26, 2003 1:49 PM
 To: Falk Hueffner
 Cc: Michael Marks; gcc-gnats@gcc.gnu.org
 Subject: Re: c/10226: unsigned short promotion with bitwise inversion
 
 
 On Wed, Mar 26, 2003 at 10:39:43PM +0100, Falk Hueffner wrote:
 > Indeed. Currently, it says:
 > warning: comparison of promoted ~unsigned with unsigned
 > Suggestion:
 > warning: comparison of ~(promoted unsigned) with unsigned
 
 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
 
 - glen
 
 ------_=_NextPart_001_01C2F3E1.B7E36740
 Content-Type: text/html;
 	charset="iso-8859-1"
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
 <HTML>
 <HEAD>
 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
 <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
 <TITLE>RE: c/10226: unsigned short promotion with bitwise inversion</TITLE>
 </HEAD>
 <BODY>
 
 <P><FONT SIZE=2>Either is far clearer than the original.&nbsp; </FONT>
 <BR><FONT SIZE=2>I like the second one better.</FONT>
 </P>
 
 <P><FONT SIZE=2>Just one other comment, are both promoted, and are both unsigned after the promotion.</FONT>
 <BR><FONT SIZE=2>I thought they are promoted to int. As per you earlier...</FONT>
 </P>
 
 <P><FONT SIZE=2>The ~ operator is subject to integer promotion,</FONT>
 <BR><FONT SIZE=2>so with the implicit conversions the expression becomes:</FONT>
 <BR><FONT SIZE=2>&nbsp; if ((int) B == ~((int) A))</FONT>
 <BR><FONT SIZE=2>which is indeed false in the example above.</FONT>
 </P>
 
 <P><FONT SIZE=2>But like I said earlier, either message below is far clearer.</FONT>
 </P>
 
 <P><FONT SIZE=2>Thanks,</FONT>
 <BR><FONT SIZE=2>Michael.</FONT>
 </P>
 
 <P><FONT SIZE=2>-----Original Message-----</FONT>
 <BR><FONT SIZE=2>From: Glen Nakamura [<A HREF="mailto:glen@imodulo.com">mailto:glen@imodulo.com</A>]</FONT>
 <BR><FONT SIZE=2>Sent: Wednesday, March 26, 2003 1:49 PM</FONT>
 <BR><FONT SIZE=2>To: Falk Hueffner</FONT>
 <BR><FONT SIZE=2>Cc: Michael Marks; gcc-gnats@gcc.gnu.org</FONT>
 <BR><FONT SIZE=2>Subject: Re: c/10226: unsigned short promotion with bitwise inversion</FONT>
 </P>
 <BR>
 
 <P><FONT SIZE=2>On Wed, Mar 26, 2003 at 10:39:43PM +0100, Falk Hueffner wrote:</FONT>
 <BR><FONT SIZE=2>&gt; Indeed. Currently, it says:</FONT>
 <BR><FONT SIZE=2>&gt; warning: comparison of promoted ~unsigned with unsigned</FONT>
 <BR><FONT SIZE=2>&gt; Suggestion:</FONT>
 <BR><FONT SIZE=2>&gt; warning: comparison of ~(promoted unsigned) with unsigned</FONT>
 </P>
 
 <P><FONT SIZE=2>How about one of these:</FONT>
 <BR><FONT SIZE=2>warning: comparison of promoted ~unsigned with unsigned is always false</FONT>
 <BR><FONT SIZE=2>warning: comparison of ~(promoted unsigned) with unsigned is always false</FONT>
 </P>
 
 <P><FONT SIZE=2>- glen</FONT>
 </P>
 
 </BODY>
 </HTML>
 ------_=_NextPart_001_01C2F3E1.B7E36740--


             reply	other threads:[~2003-03-26 21:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:06 Michael Marks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27  0:16 Michael Marks
2003-03-26 23:06 Falk Hueffner
2003-03-26 22:36 Glen Nakamura
2003-03-26 22:26 Glen Nakamura
2003-03-26 22:26 Falk Hueffner
2003-03-26 21:56 Glen Nakamura
2003-03-26 21:56 Falk Hueffner
2003-03-26 21:16 ebotcazou
2003-03-26 21:16 Michael Marks
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=20030326215601.15620.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).