This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: PR optimization/9630: [3.2/3.3/3.4 regression] crash with-freg-struct-return in C++ code
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>, gcc-gnats at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, stefan at space dot twc dot de
- Date: 12 Mar 2003 10:09:19 -0800
- Subject: Re: PR optimization/9630: [3.2/3.3/3.4 regression] crash with-freg-struct-return in C++ code
- References: <3E6F72F7.4080907@student.tudelft.nl> <jefzpslau4.fsf@sykes.suse.de>
On Wed, 2003-03-12 at 10:05, Andreas Schwab wrote:
> Steven Bosscher <s dot bosscher at student dot tudelft dot nl> writes:
>
> |> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9630
> |>
> |> This PR is about wrong code when *not* optimizing.
> |>
> |> The expected output of the test case is 2. With
> |> GCC 3.3 (todays CVS), you get:
> |>
> |> # gcc -lstdc++ -freg-struct-return 9630.cc
> |> # a.out
> |> Segmentation fault
> |> # gcc -lstdc++ -freg-struct-return 9630.cc -O
> |> # a.out
> |> 2
> |> #
> |>
> |> Could it be that this bug happens because libstdc++ was *not*
> |> compiled with --freg-struct-return?
>
> -freg-struct-return will change the ABI, so you definitely have an ABI
> mismatch here.
Good, that's what I thought. Steven, would you just mark this as "not a
bug"?
Thanks,
--
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery dot com