public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9630: [3.2/3.3/3.4 regression] crash with -freg-struct-return in C++ code
Date: Wed, 12 Mar 2003 11:16:00 -0000 [thread overview]
Message-ID: <20030312111601.22202.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/9630; it has been noted by GNATS.
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
stefan@space.twc.de, bangerth@gcc.gnu.org
Cc:
Subject: Re: optimization/9630: [3.2/3.3/3.4 regression] crash with -freg-struct-return
in C++ code
Date: Wed, 12 Mar 2003 12:08:48 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9630
Stefan, Wolfgang,
I cannot reproduce this bug with yesterdays 3.3 sources for
i586-pc-linux-gnu.
Do you still see it? Maybe this one is present on 3.2 but not 3.3? If
so, this
shouldn't be marked as a 3.3/3.4 regression.
Greetz
Steven
# gcc-3.3 -v -lstdc++ test.cc -freg-struct-return -O2
Reading specs from /opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/specs
Configured with: ../gcc-3.3/configure --disable-nls --with-gnu-as
--with-gnu-ld --prefix=/opt/experimental --program-suffix=-3.3
--enable-languages=c,c++
Thread model: posix
gcc version 3.3 20030311 (prerelease)
/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/cc1plus -quiet -v
-D__GNUC__=3 -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE
test.cc -D__GNUG__=3 -quiet -dumpbase test.cc -auxbase test -O2 -version
-freg-struct-return -o /tmp/cc1NHg6T.s
GNU C++ version 3.3 20030311 (prerelease) (i586-pc-linux-gnu)
compiled by GNU C version 3.3 20030311 (prerelease).
GGC heuristics: --param ggc-min-expand=42 --param ggc-min-heapsize=23891
ignoring nonexistent directory "/opt/experimental/i586-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/experimental/include/c++/3.3
/opt/experimental/include/c++/3.3/i586-pc-linux-gnu
/opt/experimental/include/c++/3.3/backward
/usr/local/include
/opt/experimental/include
/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/include
/usr/include
End of search list.
as -V -Qy -o /tmp/cccnvLCd.o /tmp/cc1NHg6T.s
GNU assembler version 2.11.90.0.24 (i486-suse-linux) using BFD version
2.11.90.0.24
/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/collect2 -m
elf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o
/usr/lib/crti.o
/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/crtbegin.o
-L/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3
-L/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/../../.. -lstdc++
/tmp/cccnvLCd.o -lgcc -lgcc_eh -lc -lgcc -lgcc_eh
/opt/experimental/lib/gcc-lib/i586-pc-linux-gnu/3.3/crtend.o /usr/lib/crtn.o
# LD_LIBRARY_PATH=/opt/experimental/lib/ a.out
2
next reply other threads:[~2003-03-12 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 11:16 Steven Bosscher [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:44 steven
2003-03-12 11:16 Steven Bosscher
2003-02-14 20:53 bangerth
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=20030312111601.22202.qmail@sources.redhat.com \
--to=s.bosscher@student.tudelft.nl \
--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).