This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/37763] New: bad interaction of -O3 -pg and -mcu=arm920t ??
- From: "steven dot paul at monotypeimaging dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Oct 2008 17:23:35 -0000
- Subject: [Bug c/37763] New: bad interaction of -O3 -pg and -mcu=arm920t ??
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Are there known issues among the -pg and -O3 and -mcu=arm9020t options ?
I am using Gcc 3.3.5 on Debian 1:3.3.5-13, running on a Technologic systems
TS-7200 board with an Arm920T processor.
Compiling a medium size program (~ 1.5mb source code) with flags
-O3 -mcu=arm920t -Wall
I get no errors/warnings, and the program runs to completion w/o error
Yet compiling with the flags
-O3 -pg -mcu=arm920t -Wall
produces no errors/warnings, butproduces Segment errors at runtime -- the
location of the error varies; which is unusual as the program is deterministic.
And compiling with the flags
-O3 -g -mcu=arm920t -Wall
produces no errors/warnings, and runs to completion (either at command line or
inside gdb) w/o error.
fiy ... compiling the program with these sets of flags
-mcu-arm920t -Wall
and
-03 -mcu=arm920t -Wall
compile with no errors/warnings, run to completion w/o error, and and produces
identical large (~2gB) regression test output.
If there are no known issues among these flags, I'll work to get a smaller code
base which will reproduce the bug.
thanks...
--
Summary: bad interaction of -O3 -pg and -mcu=arm920t ??
Product: gcc
Version: 3.3.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: steven dot paul at monotypeimaging dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37763