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/48308] [4.6/4.7 Regression] crosscompiling to arm fails with assembler: can't resolve '.LC4' {.rodata.str1.1 section} - '.LPIC4' {*UND* section}
Date: Fri, 06 Jan 2012 16:04:00 -0000	[thread overview]
Message-ID: <bug-48308-4-DpGoNEouvi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48308-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-01-06 16:02:49 UTC ---
I think it would be better to just generate a single insn early on and then to
split it once the loop optimizers have had a chance to run.  Then the
optimizers should be able to throw the whole expression away if it's not needed
and hoist it as a whole if it's inside a loop.

Splitting it before sched1 would be ideal, but the split could be delayed until
after reload if necessary.


  parent reply	other threads:[~2012-01-06 16:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  5:20 [Bug c/48308] New: " dev-gcc-20110327-b588 at gheift dot de
2011-03-28  8:13 ` [Bug target/48308] " mikpe at it dot uu.se
2011-03-28 12:45 ` dev-gcc-20110327-b588 at gheift dot de
2011-03-28 13:21 ` mikpe at it dot uu.se
2011-03-28 23:43 ` mikpe at it dot uu.se
2011-03-28 23:54 ` mikpe at it dot uu.se
2011-03-29 15:44 ` ibolton at gcc dot gnu.org
2011-06-22 15:15 ` m.k.edwards at gmail dot com
2011-06-24  9:15 ` [Bug target/48308] [4.6 regression] " ramana at gcc dot gnu.org
2011-08-01 14:26 ` rguenth at gcc dot gnu.org
2011-08-17 20:51 ` [Bug target/48308] [4.6/4.7 Regression] " jsm28 at gcc dot gnu.org
2011-09-07  7:55 ` pinskia at gcc dot gnu.org
2011-09-07 10:56 ` ramana at gcc dot gnu.org
2011-09-13  6:32 ` ramana at gcc dot gnu.org
2011-10-26 17:55 ` jakub at gcc dot gnu.org
2011-11-02 11:39 ` madhu_k515 at yahoo dot co.in
2011-11-02 11:42 ` ramana at gcc dot gnu.org
2011-12-22 16:09 ` jakub at gcc dot gnu.org
2011-12-22 16:21 ` michael.hope at linaro dot org
2012-01-05 17:48 ` jakub at gcc dot gnu.org
2012-01-06 16:04 ` rearnsha at gcc dot gnu.org [this message]
2012-01-11 18:17 ` ramana at gcc dot gnu.org
2012-01-13  9:11 ` ramana at gcc dot gnu.org
2012-01-25  9:47 ` ramana at gcc dot gnu.org
2012-03-01 15:28 ` jakub at gcc dot gnu.org
2012-05-31  0:53 ` [Bug target/48308] [4.6/4.7/4.8 " breakpoint at runbox dot com
2012-12-31  9:56 ` pinskia at gcc dot gnu.org
2013-03-10  9:20 ` mh+gcc at glandium dot org
2013-03-13 20:55 ` [Bug target/48308] [4.6 " steven at gcc dot gnu.org
2013-03-22  8:29 ` sebastian.huber@embedded-brains.de
2013-03-22 10:00 ` ramana at gcc dot gnu.org
2013-04-05  8:32 ` ramana 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-48308-4-DpGoNEouvi@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).