public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40523] GCC generates invalid instructions when building for Thumb-2 on armel Date: Thu, 09 Jul 2009 19:03:00 -0000 [thread overview] Message-ID: <20090709190307.1544.qmail@sourceware.org> (raw) In-Reply-To: <bug-40523-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from mikpe at it dot uu dot se 2009-07-09 19:03 ------- This was fixed for 4.4.0 by Richard's r143339. I backported that to 4.3.4 and it built ok and fixed this test case. My boxes are ARMv5TE so I cannot run the generated thumb2 code however. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40523
next prev parent reply other threads:[~2009-07-09 19:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-22 23:21 [Bug target/40523] New: " doko at ubuntu dot com 2009-06-22 23:24 ` [Bug target/40523] " doko at ubuntu dot com 2009-06-22 23:30 ` rearnsha at gcc dot gnu dot org 2009-07-09 19:03 ` mikpe at it dot uu dot se [this message] 2010-03-20 19:29 ` ramana at gcc dot gnu dot org 2010-05-22 19:01 ` rguenth at gcc dot gnu dot org [not found] <bug-40523-4@http.gcc.gnu.org/bugzilla/> 2011-04-28 16:37 ` rguenth at gcc dot gnu.org 2013-08-05 20:40 ` ramana at gcc dot gnu.org 2013-08-06 8:33 ` rearnsha 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=20090709190307.1544.qmail@sourceware.org \ --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).