public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnugcc at emblocks dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56441] [ARM Thumb] generated asm code produces "branch out of range" error in gas with -O1 -mcpu=cortex-m3
Date: Tue, 26 Feb 2013 17:51:00 -0000	[thread overview]
Message-ID: <bug-56441-4-3Vbjsp4VWf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56441-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56441

--- Comment #11 from gnugcc at emblocks dot org 2013-02-26 17:51:16 UTC ---
Richard, you can close this one.

I'm leaving the ARM-branch and are moving to the head of branch 4.7.

Sorry for the inconveniences, I thought that the ARM branch would be the most
suitable for ARM but I discovered that that relationship isn't that obvious.

At least I learned today a little of the GCC internals.

Sorry again.

Gerard


  parent reply	other threads:[~2013-02-26 17:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  8:25 [Bug target/56441] New: " gnugcc at emblocks dot org
2013-02-25  8:31 ` [Bug target/56441] " gnugcc at emblocks dot org
2013-02-25  9:14 ` jakub at gcc dot gnu.org
2013-02-25 11:36 ` gnugcc at emblocks dot org
2013-02-25 11:41 ` gnugcc at emblocks dot org
2013-02-25 13:15 ` gnugcc at emblocks dot org
2013-02-25 16:48 ` gnugcc at emblocks dot org
2013-02-26  9:06 ` gnugcc at emblocks dot org
2013-02-26 17:02 ` rearnsha at gcc dot gnu.org
2013-02-26 17:03 ` rearnsha at gcc dot gnu.org
2013-02-26 17:25 ` gnugcc at emblocks dot org
2013-02-26 17:51 ` gnugcc at emblocks dot org [this message]
2013-03-05  7:07 ` 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=bug-56441-4-3Vbjsp4VWf@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).