public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Manfred Hollstein <manfredh@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6453: g++ regression in 3.1 Date: Thu, 25 Apr 2002 08:36:00 -0000 [thread overview] Message-ID: <20020425153602.19839.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6453; it has been noted by GNATS. From: Manfred Hollstein <manfredh@redhat.com> To: green@redhat.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/6453: g++ regression in 3.1 Date: Thu, 25 Apr 2002 17:31:36 +0200 green@redhat.com wrote: >>Number: 6453 >>Category: c++ >>Synopsis: g++ regression in 3.1 >>Confidential: no >>Severity: non-critical >>Priority: medium >>Responsible: unassigned >>State: open >>Class: ice-on-illegal-code >>Submitter-Id: net >>Arrival-Date: Thu Apr 25 08:16:00 PDT 2002 >>Closed-Date: >>Last-Modified: >>Originator: Anthony Green >>Release: 3.1 20020424 (prerelease) >>Organization: >>Environment: > > System: Linux louie 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown > Architecture: i686 > > > host: i686-pc-linux-gnu > build: i686-pc-linux-gnu > target: i686-pc-linux-gnu > configured with: /louie/green/3.1/gcc/configure --prefix=/louie/green/3.1/i --enable-threads --enable-languages=c,c++,java : (reconfigured) : (reconfigured) Hmm, my snapshot from yesterday's branch in CVS (2002/04/24 10:12:11 +0200) works without generating an ICE. I did a clean build of everything, though, ie. I don't have any (reconfigured) notes. My full Configure with: line reads like this: Configured with: ../gcc-3.1/configure --host=i686-redhat7-linux-gnu --target=i686-redhat7-linux-gnu --build=i686-redhat7-linux-gnu --srcdir=../gcc-3.1 --prefix=/opt/gnu --exec-prefix=/opt/gnu/H-ia32-linux --with-gnu-as --with-gnu-ld --disable-checking --enable-clocale=gnu --enable-interpreter --enable-shared --enable-threads=posix --with-system-zlib --with-local-prefix=/opt/gnu --enable-languages=c++,java,ada --enable-nls --verbose Cheers. l8er manfred > >>Description: > > Given the following nonsense code... > > void *foo() > { > char x[100]; > x++; > return (void *) x; > } > > Red Hat's g++ 2.96 reports: > > $ g++ -c c.cc > c.cc: In function `void *foo ()': > c.cc:4: non-lvalue in increment > c.cc:3: warning: address of local variable `x' returned > > Unfortunately I don't have an older FSF release handy to test on (like > 2.95, or 3.0), so I don't know what they do. However, the current 3.1 > branch says: > > $ g++ -c c.cc > non-lvalue > > in > > increment > > address > > of > > local > > variable > > ` > Internal compiler error: Error reporting routines re-entered. > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. > > > >>How-To-Repeat: > > Compile the following with g++: > > void *foo() > { > char x[100]; > x++; > return (void *) x; > } > > >>Fix: > > > >>Release-Note: >>Audit-Trail: >>Unformatted: > >
next reply other threads:[~2002-04-25 15:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-25 8:36 Manfred Hollstein [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-26 14:02 green 2002-04-25 8:16 green
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=20020425153602.19839.qmail@sources.redhat.com \ --to=manfredh@redhat.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: linkBe 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).