public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arnaud.patard@rtp-net.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48090] gcc 4.5.2 miscompilation when building on arm Date: Sat, 12 Mar 2011 12:16:00 -0000 [thread overview] Message-ID: <bug-48090-4-cuIfBHF8I5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48090-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48090 --- Comment #3 from arnaud patard <arnaud.patard@rtp-net.org> 2011-03-12 12:16:12 UTC --- (In reply to comment #2) > I get correct-looking code on armv5tel-linux with vanilla gcc-4.6-20110305 and > gcc-4.5-20110310, with 4.4 the code looks different but not obviously broken. I said -march=armv5t (or -march=armv4t I guess). It's important as -march=armv5te won't trigger the bug. > > Can you make the test case standalone and include a runtime check for the > possible miscompilation? My test case was to build tar and run the delete01.at check but it's not really a standalone test. So far, I've not managed to have a test case small than compiling the preprocessed file. > > How was your gcc configured? I reproduce it with my gcc and debian gcc 4.5.2 so I believe this rules out misconfiguration.
next prev parent reply other threads:[~2011-03-12 12:16 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-12 9:01 [Bug c/48090] New: " arnaud.patard@rtp-net.org 2011-03-12 9:02 ` [Bug c/48090] " arnaud.patard@rtp-net.org 2011-03-12 12:03 ` mikpe at it dot uu.se 2011-03-12 12:16 ` arnaud.patard@rtp-net.org [this message] 2011-03-12 15:42 ` mikpe at it dot uu.se 2011-03-12 17:38 ` mikpe at it dot uu.se 2011-03-12 21:33 ` mikpe at it dot uu.se 2011-03-13 15:09 ` mikpe at it dot uu.se 2011-03-13 19:33 ` mikpe at it dot uu.se 2011-03-13 20:40 ` arnaud.patard@rtp-net.org 2011-03-14 10:32 ` [Bug target/48090] [4.5 Regression] " rguenth at gcc dot gnu.org 2011-04-10 10:42 ` rguenth at gcc dot gnu.org 2011-04-11 10:24 ` ramana at gcc dot gnu.org 2011-04-12 13:43 ` ramana at gcc dot gnu.org 2011-04-12 13:53 ` ramana at gcc dot gnu.org 2011-04-12 13:53 ` ramana at gcc dot gnu.org 2011-04-12 13:56 ` froydnj at codesourcery dot com 2011-04-13 7:41 ` ramana at gcc dot gnu.org 2011-04-13 7:56 ` ramana at gcc dot gnu.org 2011-04-27 10:08 ` ramana at gcc dot gnu.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-48090-4-cuIfBHF8I5@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).