public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven dot paul at monotypeimaging dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37763] New: bad interaction of -O3 -pg and -mcu=arm920t ?? Date: Tue, 07 Oct 2008 17:24:00 -0000 [thread overview] Message-ID: <bug-37763-16799@http.gcc.gnu.org/bugzilla/> (raw) 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
next reply other threads:[~2008-10-07 17:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-07 17:24 steven dot paul at monotypeimaging dot com [this message] 2008-10-07 20:37 ` [Bug target/37763] " pinskia at gcc dot gnu dot org 2009-04-29 17:30 ` ramana at gcc dot gnu dot org 2009-10-15 8:30 ` ramana at gcc dot gnu dot org 2009-10-15 8:31 ` ramana at gcc dot gnu dot org
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=bug-37763-16799@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).