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: Sat, 18 Feb 2012 15:34:00 -0000	[thread overview]
Message-ID: <bug-52294-4-ZPjHTPS9nf@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

Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|unassigned at gcc dot       |rearnsha at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-02-18 15:25:01 UTC ---
(In reply to comment #3)
> Richard, I suppose you mean the problem is in this define_insn:
> 
> (define_insn "*thumb1_ashlsi3"
>   [(set (match_operand:SI            0 "register_operand" "=l,l")
>         (ashift:SI (match_operand:SI 1 "register_operand" "l,0")
>                    (match_operand:SI 2 "nonmemory_operand" "N,l")))]
>   "TARGET_THUMB1"
>   "lsl\\t%0, %1, %2"
>   [(set_attr "length" "2")
>    (set_attr "conds" "set")])

No, that pattern is only for Thumb1, it never applies to Thumb2.

I'm currently testing a fix


  parent reply	other threads:[~2012-02-18 15:25 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 [this message]
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
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-ZPjHTPS9nf@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: link
Be 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).