public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Brian Ceccarelli" <brian@talusmusic.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/6568: g++3 (3.0.2) misinterpreting single byte hex constants
Date: Mon, 06 May 2002 06:26:00 -0000	[thread overview]
Message-ID: <20020506132604.11986.qmail@sources.redhat.com> (raw)

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

From: "Brian Ceccarelli" <brian@talusmusic.com>
To: <neil@gcc.gnu.org>,
	<brian@talusmusic.com>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: c++/6568: g++3 (3.0.2) misinterpreting single byte hex constants
Date: Mon, 6 May 2002 09:20:59 -0400

 Subject: Re: c++/6568: g++3 (3.0.2) misinterpreting single byte hex
 
 ************************************
 localhost:[17] /home/ceccareb/work % uname -a
 Linux localhost.localdomain 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686
 unknown
 
 localhost:[18] /home/ceccareb/work %  g++3 -v
 Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.0.2/specs
 Configured with:
 ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
  --enable-shared --enable-threads=posix --disable-checking --host=i386-redha
 t-linux
 Thread model: posix
 gcc version 3.0.2 20010905 (Red Hat Linux 7.1 3.0.1-3)
 localhost:[42] /usr/src %
 
 
 localhost:[19] /home/ceccareb/work % cat test.cc
 # include <stdio.h>
 
 
 int main(int argc, char *argv[])
 {
 
    int      i;
    char     n;
 
    i = 0;
    n = (-1);
 
 
    printf("sizeof(i) = %d\n", sizeof i);
    printf("sizeof(n) = %d\n", sizeof n);
 
    if (n == 0xFF)
       printf("Yes.  n = 0x%x\n", n);
    else
       printf("No.  n = 0x%x\n", n);
 
    return 0;
 
 }
 
 
 
 localhost:[20] /home/ceccareb/work % g++3 test.cc
 test.cc: In function `int main(int, char**)':
 test.cc:17: warning: comparison is always false due to limited range of data
    type
 
 
 localhost:[21] /home/ceccareb/work % a.out
 sizeof(i) = 4
 sizeof(n) = 1
 No.  n = 0xffffffff
 
 localhost:[22] /home/ceccareb/work %
 
 **************************************
 
 
 -----Original Message-----
 From: neil@gcc.gnu.org [mailto:neil@gcc.gnu.org]
 Sent: Monday, May 06, 2002 4:26 AM
 To: brian@talusmusic.com; gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org;
 nobody@gcc.gnu.org
 Subject: Re: c++/6568: g++3 (3.0.2) misinterpreting single byte hex
 constants
 
 
 Synopsis: g++3 (3.0.2) misinterpreting single byte hex constants
 
 State-Changed-From-To: open->feedback
 State-Changed-By: neil
 State-Changed-When: Mon May  6 01:26:16 2002
 State-Changed-Why:
     Missing testcase.  Please reply to this e-mail with the
     5-line test case in the body of your e-mail; without changing the
 subject line or the cc: list.  That will ensure it goes into our bug system.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=6568
 


             reply	other threads:[~2002-05-06 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06  6:26 Brian Ceccarelli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-06 13:50 neil
2002-05-06  8:26 Neil Booth
2002-05-06  5:26 Brian Ceccarelli
2002-05-06  1:26 neil
2002-05-05 20:16 brian

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=20020506132604.11986.qmail@sources.redhat.com \
    --to=brian@talusmusic.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).