public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.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:36:00 -0000	[thread overview]
Message-ID: <20030326223600.8561.qmail@sources.redhat.com> (raw)

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

From: Glen Nakamura <glen@imodulo.com>
To: 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 12:30:54 -1000

 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...)
 > 
 > -- 
 > 	Falk
 
 It does on my system (GCC 3.3):
 
 .LC1:
         .string "Fail"
         .text
         .p2align 4,,15
 .globl main
         .type   main, @function
 main:
         pushl   %ebp
         movl    %esp, %ebp
         subl    $8, %esp
         andl    $-16, %esp
         movl    $.LC1, (%esp)
         call    puts
         movl    %ebp, %esp
         xorl    %eax, %eax
         popl    %ebp
         ret
 
 But, as I mentioned before my suggestion won't work for other comparisons...
 the warning probably needs to be generic enough for all of the following cases:
 unsigned (char|short) (==|!=|<|<=|>|>=) ~unsigned (char|short)
 which is *not* always false but could have unexpected results.
 
 - glen


             reply	other threads:[~2003-03-26 22:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:36 Glen Nakamura [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:26 Falk Hueffner
2003-03-26 22:26 Glen Nakamura
2003-03-26 22:06 Michael Marks
2003-03-26 21:56 Falk Hueffner
2003-03-26 21:56 Glen Nakamura
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=20030326223600.8561.qmail@sources.redhat.com \
    --to=glen@imodulo.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).