public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19457] [4.0 Regression] Warning depends on cached constant
Date: Sat, 15 Jan 2005 18:10:00 -0000	[thread overview]
Message-ID: <20050115180955.23259.qmail@sourceware.org> (raw)
In-Reply-To: <20050115123233.19457.reichelt@gcc.gnu.org>


------- Additional Comments From schlie at comcast dot net  2005-01-15 18:09 -------
(In reply to comment #4)

(again sorry), nor should ~0 be considred equivelent to -1, any more than any explicit
non-signed constant like 0xFFFF for example be (as previously questioned), as such
values only have equivelent representations if the constant's required representation
precision happens to be the same as the targets specifed int type-sizes; therefore
would not be reasonably target portable if treated otherwise.

(assuming for the sake of argument if sizeof(int) = 2, sizeof(long) = 4):

 unsigned long = (assumed signed int compatibe) -1, long == 0xFFFFFFFF
 unsigend long = (assumed unsigned int compatible)~0, long == 0x000FFFF



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19457


  parent reply	other threads:[~2005-01-15 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 12:32 [Bug c++/19457] New: " reichelt at gcc dot gnu dot org
2005-01-15 16:49 ` [Bug c++/19457] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-15 17:07 ` schlie at comcast dot net
2005-01-15 17:17 ` schlie at comcast dot net
2005-01-15 17:36 ` schlie at comcast dot net
2005-01-15 18:10 ` schlie at comcast dot net [this message]
2005-01-18  1:02 ` pinskia at gcc dot gnu dot org
2005-01-29  2:46 ` mmitchel at gcc dot gnu dot org
2005-01-31  1:17 ` cvs-commit at gcc dot gnu dot org
2005-01-31  1:22 ` mmitchel at gcc dot gnu dot org

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=20050115180955.23259.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).