This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug rtl-optimization/33676] libgfortran bootstrap failure: selected_int_kind.f90:22: Segmentation fault, wrong code with -fomit-frame-pointer
- From: Serge Belyshev <belyshev at depni dot sinp dot msu dot ru>
- To: "Uros Bizjak" <ubizjak at gmail dot com>
- Cc: "Kenneth Zadeck" <zadeck at naturalbridge dot com>, "GCC Patches" <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 12 Oct 2007 10:13:36 +0400
- Subject: Re: [Bug rtl-optimization/33676] libgfortran bootstrap failure: selected_int_kind.f90:22: Segmentation fault, wrong code with -fomit-frame-pointer
- References: <5787cf470710112257u7fcaceaq5024864321fb8232@mail.gmail.com>
"Uros Bizjak" <ubizjak@gmail.com> writes:
> Hello!
>
>> 2007-10-11 Kenneth Zadeck <zadeck@naturalbridge.com>
>
>> PR middle-end/33676
>> * gcc.dg/torture/pr33676.c: New.
>
> This is wrong place for tests that fail with "-fomit-frame-pointer".
> dg-torture will cycle all optimization levels, but
> -fomit-frame-pointer will be checked only at -O3. However, since we
> know that the testcase fails with "-O0 -fomit-frame-pointer", gcc.dg
> is a better place for this.
But as the bug fixed, it doesn't fail anymore. So this is in torture,
compiled several times, using different options, testing for *another*
(possibly similar, but doesn't matter) regression to appear.
Also note that original bug failed not only with -O0 -fomit-frame-pointer
but also with any of: -O{0,1,2,3} -fomit-frame-pointer -march=i{3,4,5}86
So gcc.dg/torture/ is the right place for that testcase.