public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/258
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010114213600.9174.qmail@sourceware.cygnus.com> (raw)

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

From: neil@gcc.gnu.org
To: HPENNER@de.ibm.com, gcc-gnats@gcc.gnu.org,
  martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/258
Date: 14 Jan 2001 21:35:56 -0000

 Synopsis: Exception handling bug
 
 State-Changed-From-To: analyzed->closed
 State-Changed-By: neil
 State-Changed-When: Sun Jan 14 13:35:56 2001
 State-Changed-Why:
     With CVS G++:
     
     bash-2.04$ g++ -fsjlj-exceptions -O2 /tmp/test.C
     bash-2.04$ 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=258&database=gcc
>From jsm28@cam.ac.uk Sun Apr 01 00:00:00 2001
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: c/1609: -funsigned-char -fsigned-char defines __CHAR_UNSIGNED__
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <E14GRKg-0003zz-00@jsm28.trin.cam.ac.uk>
X-SW-Source: 2001-q1/msg00175.html
Content-length: 1464

>Number:         1609
>Category:       c
>Synopsis:       -funsigned-char -fsigned-char defines __CHAR_UNSIGNED__
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 10 11:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        2.97 20010110 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.18 #1 Sun Jan 7 21:04:55 UTC 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:

This is a PR to track an issue previously reported on gcc-bugs
<URL: http://gcc.gnu.org/ml/gcc-bugs/2000-11/msg00545.html >.  When
-funsigned-char -fsigned-char is used on a system with signed chars,
chars are signed but __CHAR_UNSIGNED__ is defined.

>How-To-Repeat:

See message cited.

>Fix:

Either leave until specs / option parsing get redesigned, or kludge
something so that the existing code that knows (when handling specs)
that -f<foo> and -fno-<foo> are opposites also knows that
-fsigned-char and -funsigned-char are opposites (and similarly,
-ffreestanding and -fhosted, with similar problems associated with
__STDC_HOSTED__).
>Release-Note:
>Audit-Trail:
>Unformatted:
>From aoliva@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: aoliva@gcc.gnu.org
To: aoliva@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1898
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010311191601.6098.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02226.html
Content-length: 677

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

From: aoliva@gcc.gnu.org
To: aoliva@gcc.gnu.org, fleming.151@osu.edu, gcc-gnats@gcc.gnu.org,
  nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/1898
Date: 11 Mar 2001 19:15:50 -0000

 Synopsis: problems compiling with varargs
 
 Responsible-Changed-From-To: unassigned->aoliva
 Responsible-Changed-By: aoliva
 Responsible-Changed-When: Sun Mar 11 11:15:50 2001
 Responsible-Changed-Why:
     This is a regression from 2.95.2.  I've asked Bruce Korb for help with this one.  I'm assigning it to myself so that I can find it easily later.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1898&database=gcc


                 reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010114213600.9174.qmail@sourceware.cygnus.com \
    --to=neil@gcc.gnu.org \
    --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).