public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52294] [4.7 Regression] [ARM Thumb] generated asm code produces "branch out of range" error in gas with -Os -mcpu=cortex-a9 Date: Tue, 21 Feb 2012 23:47:00 -0000 [thread overview] Message-ID: <bug-52294-4-KBBp4GGyyz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52294-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52294 --- Comment #9 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-02-21 23:46:10 UTC --- Author: rearnsha Date: Tue Feb 21 23:46:05 2012 New Revision: 184452 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184452 Log: PR target/52294 * thumb2.md (thumb2_shiftsi3_short): Split register and immediate shifts. For register shifts tie operands 0 and 1. (peephole2 for above): Check that register-controlled shifts have suitably tied operands. Modified: branches/gcc-4_6-branch/gcc/ChangeLog branches/gcc-4_6-branch/gcc/config/arm/thumb2.md
next prev parent reply other threads:[~2012-02-21 23:47 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-17 10:32 [Bug target/52294] New: " bero at arklinux dot org 2012-02-17 10:51 ` [Bug target/52294] " mikpe at it dot uu.se 2012-02-17 23:23 ` steven at gcc dot gnu.org 2012-02-18 0:00 ` rearnsha at gcc dot gnu.org 2012-02-18 12:32 ` steven at gcc dot gnu.org 2012-02-18 12:46 ` steven at gcc dot gnu.org 2012-02-18 12:47 ` steven at gcc dot gnu.org 2012-02-18 13:24 ` steven at gcc dot gnu.org 2012-02-18 15:34 ` rearnsha at gcc dot gnu.org 2012-02-20 12:31 ` rguenth at gcc dot gnu.org 2012-02-21 15:53 ` rearnsha at gcc dot gnu.org 2012-02-21 23:47 ` rearnsha at gcc dot gnu.org [this message] 2012-02-22 0:05 ` rearnsha at gcc dot gnu.org 2012-02-22 1:39 ` rearnsha at gcc dot gnu.org 2012-06-08 8:58 ` jye2 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-52294-4-KBBp4GGyyz@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).