public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40523] New: GCC generates invalid instructions when building for Thumb-2 on armel Date: Mon, 22 Jun 2009 23:21:00 -0000 [thread overview] Message-ID: <bug-40523-11764@http.gcc.gnu.org/bugzilla/> (raw) [ forwarded from https://launchpad.net/+bugs/347864 ] seen on the 4.3 branch, fixed in 4.4 and trunk. When building for the Thumb-2 instruction set, GCC appears to generate Thumb2 loads and stores with invalid address offsets and base register writeback. The Thumb-2 instruction set does not support the full offset range for these instructions, causing the assembler to fail. The failure is observed as follows: g++ -march=armv7 -mthumb -O2 -c asbug.c++ /tmp/ccrSTYGR.s:525: Error: offset out of range Line 545 of the generated assembler is: ldr r2, [sl, #264]! However, the allowed offset range for this instruction is restricted to be <256. -- Summary: GCC generates invalid instructions when building for Thumb-2 on armel Product: gcc Version: 4.3.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: doko at ubuntu dot com GCC target triplet: arm-linux-gnueabi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40523
next reply other threads:[~2009-06-22 23:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-22 23:21 doko at ubuntu dot com [this message] 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 2010-03-20 19:29 ` ramana at gcc dot gnu dot org 2010-05-22 19:01 ` rguenth 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-40523-11764@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).