public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43961] [4.6/4.7/4.8 Regression] [ARM thumb] "branch out of range" with thumb1_output_casesi
Date: Wed, 09 Jan 2013 21:55:00 -0000	[thread overview]
Message-ID: <bug-43961-4-WvWpaiY425@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43961-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #11 from Joseph S. Myers <jsm28 at gcc dot gnu.org> 2013-01-09 21:55:08 UTC ---
Created attachment 29133
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29133
More complicated fix for 4.6

The previous proposed patch breaks Thumb-2, because alignments for labels get
set based on ADDR_VEC_ALIGN before jump tables get shortened from SImode to a
narrower mode, and not updated afterwards so there is spurious alignment
between a tbb instruction and a jump table.  This patch adds code to
shorten_branches to allow for this issue.  4.6-based; I'll test for mainline.


  parent reply	other threads:[~2013-01-09 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43961-4@http.gcc.gnu.org/bugzilla/>
2013-01-03  0:00 ` [Bug target/43961] " jsm28 at gcc dot gnu.org
2013-01-03  8:55 ` mikpe at it dot uu.se
2013-01-03 16:20 ` [Bug target/43961] [4.6/4.7/4.8 Regression] " jsm28 at gcc dot gnu.org
2013-01-07 15:19 ` rguenth at gcc dot gnu.org
2013-01-09 21:55 ` jsm28 at gcc dot gnu.org [this message]
2013-01-15 16:18 ` jsm28 at gcc dot gnu.org
2013-01-15 16:22 ` [Bug target/43961] [4.6/4.7 " jsm28 at gcc dot gnu.org
2013-04-12 15:15 ` [Bug target/43961] [4.7 " jakub at gcc dot gnu.org
2014-06-12 12:56 ` rguenth 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-43961-4-WvWpaiY425@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).