public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Richard Henderson <rth@cygnus.com>
Cc: gcc@gcc.gnu.org
Subject: Re: comparisons..
Date: Fri, 14 Jul 2000 12:43:00 -0000	[thread overview]
Message-ID: <396F638E.FBA1A229@moene.indiv.nluug.nl> (raw)
In-Reply-To: <20000714105706.B8485@cygnus.com>

Richard Henderson wrote:

> On Fri, Jul 14, 2000 at 01:14:59PM +0200, Toon Moene wrote:
> > I always wondered whether it would be possible to drop the warning in
> > case the signed constant has the same value when interpreted as an
> > unsigned value.

> We do do this.

Well, the simple example works, but then why does gcc warn on
loop.c:9839:

             && VARRAY_INT (n_times_set, REGNO (SET_DEST (set))) == 1

?

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

  reply	other threads:[~2000-07-14 12:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 22:58 comparisons Andrew Morton
2000-07-12 23:35 ` comparisons Michael Meissner
2000-07-12 23:48   ` comparisons Andrew Morton
2000-07-12 23:57     ` comparisons Michael Meissner
2000-07-13  0:24       ` comparisons Andrew Morton
2000-07-13  1:05         ` comparisons Nick Burrett
2000-07-13  1:47           ` comparisons Andrew Morton
2000-07-13  9:12             ` comparisons Joe Buck
2000-07-13 14:48               ` comparisons Andi Kleen
2000-07-13 21:46               ` comparisons Andrew Morton
2000-07-13  0:24     ` comparisons Martin v. Loewis
2000-07-13  1:09       ` comparisons Andrew Morton
2000-07-13  1:36         ` comparisons Nick Burrett
2000-07-13  1:47           ` comparisons Andrew Morton
2000-07-13  6:39         ` comparisons Andrew Morton
2000-07-13  9:11           ` comparisons Joe Buck
2000-07-13  9:45             ` comparisons Bruce Korb
2000-07-13 10:32               ` comparisons Joe Buck
2000-07-13 15:14             ` comparisons Russ Allbery
2000-07-13 17:11               ` comparisons Philipp Thomas
2000-07-28  5:48           ` comparisons Nix
2000-07-13  9:44         ` comparisons Gerald Pfeifer
2000-07-13 17:12           ` comparisons Andrew Morton
2000-07-13 17:30             ` comparisons Russ Allbery
2000-07-13 17:48               ` comparisons Michael Meissner
2000-07-14  4:22             ` comparisons Toon Moene
2000-07-14 10:57               ` comparisons Richard Henderson
2000-07-14 12:43                 ` Toon Moene [this message]
2000-07-14 12:52                   ` comparisons Richard Henderson
2000-07-14 13:53                     ` comparisons Toon Moene
2000-07-14 14:00               ` comparisons Martin v. Loewis
2000-07-15 17:35               ` comparisons Joe Buck
2000-07-12 23:54 ` comparisons Martin v. Loewis
2000-07-13 10:09 comparisons Phil Edwards
2000-07-13 11:18 ` comparisons Michael Meissner

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=396F638E.FBA1A229@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@cygnus.com \
    /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).