BUG: -fomit-frame-pointer & C++ w/ exceptions still broken on i?86-linux-gnu

Manfred Hollstein manfredh@redhat.com
Sun Dec 3 07:42:00 GMT 2000


Hi there,

I just submitted my testresults for i[56]86-redhat7-linux-gnu systems.
I did two runs which only  differed in using "-fomit-frame-pointer" in
BOOT_CFLAGS and CXXFLAGS.  Interestingly,  there are additional faults
when "-fomit-frame-pointer" is used (diff listing below).

Sources:	  - gcc mainline from CVS last updated at
		    2000/12/03 10:50:06 +0100
Patches:	  None.
Environment:	  - autoconf-2.13-9
		  - automake-1.4-8
		  - binutils-20001201 via anonymous CVS from
		    anoncvs.cygnus.com
		  - dejagnu-20000815 via anonymous CVS from
		    anoncvs.cygnus.com
		  - Red Hat Linux 7 + recommended updates as of today
		  - Kernel 2.2.16-22 (compiled by "gcc version
		    egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)")
		  - glibc-2.2-5
		  - glibc-devel-2.2-5
configure flags:  --host=i586-redhat7-linux-gnu --target=i586-redhat7-linux-gnu --build=i586-redhat7-linux-gnu --srcdir=../gcc-20001203 --prefix=/opt/gnu --exec-prefix=/opt/gnu/H-ia32-linux --with-gnu-as --with-gnu-ld --disable-checking --enable-shared --enable-threads=posix --with-system-zlib --with-local-prefix=/opt/gnu --enable-languages=c,gcov,c++ --enable-nls --verbose

#1:
BOOT_CC:	  gcc version 2.95.3 19991030 (prerelease)
BOOT_CFLAGS:	  -O2 -march=pentium -fomit-frame-pointer
CFLAGS:		  -O2 -march=pentium -fomit-frame-pointer
CXXFLAGS:	  -O2 -march=pentium -fomit-frame-pointer -g

#2:
BOOT_CC:	  gcc version 2.95.3 19991030 (prerelease)
BOOT_CFLAGS:	  -O2 -march=pentium
CFLAGS:		  -O2 -march=pentium -fomit-frame-pointer
CXXFLAGS:	  -O2 -march=pentium -g

$ diff ./#1 ./#2
27c27
< -r	-r	21_strings/append.cc
---
> -r	+	21_strings/append.cc
31,32c31,32
< +	-r	21_strings/ctor_copy_dtor.cc
< +	-r	21_strings/element_access.cc
---
> +	+	21_strings/ctor_copy_dtor.cc
> +	+	21_strings/element_access.cc
34c34
< +	-r	21_strings/insert.cc
---
> +	+	21_strings/insert.cc
41c41
< +	-r	21_strings/substr.cc
---
> +	+	21_strings/substr.cc
61c61
< +	-r	23_containers/vector_element_access.cc
---
> +	+	23_containers/vector_element_access.cc
82c82
< -r	-r	27_io/ios_members.cc
---
> -r	+	27_io/ios_members.cc
149,151d148
< FAIL: g++.abi/cxa_vec.C  Execution test
< FAIL: g++.eh/spec2.C  Execution test
< FAIL: g++.eh/spec3.C  Execution test
154,158d150
< FAIL: g++.mike/dyncast1.C  Execution test
< FAIL: g++.mike/dyncast2.C  Execution test
< FAIL: g++.mike/eh33.C  Execution test
< FAIL: g++.mike/eh50.C  Execution test
< FAIL: g++.mike/eh51.C  Execution test
163,164c155,156
< # of expected passes		6139
< # of unexpected failures	11
---
> # of expected passes		6147
> # of unexpected failures	3


I sent a similar report in August, please see thread at

< http://gcc.gnu.org/ml/gcc-bugs/2000-08/msg00440.html >

I believe, this ought to be fixed for gcc-3.0.

Thoughts?

Cheers, manfred.


More information about the Gcc-bugs mailing list