public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: neil@daikokuya.demon.co.uk
Cc: gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Strange sign-compare results
Date: Sun, 16 Dec 2001 17:59:00 -0000	[thread overview]
Message-ID: <200112170151.UAA01430@caip.rutgers.edu> (raw)

 > From: Neil Booth <neil@daikokuya.demon.co.uk>
 > 
 > neil wrote:-
 > 
 > > The others convert the unsigned operand to signed, and therefore the
 > > result of the subtraction is signed.
 > 
 > Ignore that last sentence; I didn't read your examples closely enough
 > 8-)
 > Neil.

I'm not sure what you mean then.  Would you say the behavior I
observed is a bug or feature?

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions

             reply	other threads:[~2001-12-17  1:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 17:59 Kaveh R. Ghazi [this message]
2001-12-17  0:02 ` Neil Booth
  -- strict thread matches above, loose matches on Subject: below --
2001-12-16 13:46 Kaveh R. Ghazi
2001-12-16 13:57 ` Neil Booth
2001-12-16 15:17   ` Neil Booth

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=200112170151.UAA01430@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.demon.co.uk \
    /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).