public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/61635] New: LTO partitioner does not handle &&label in statics
Date: Fri, 27 Jun 2014 21:26:00 -0000	[thread overview]
Message-ID: <bug-61635-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61635

            Bug ID: 61635
           Summary: LTO partitioner does not handle &&label in statics
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: andi-gcc at firstfloor dot org

I currently don't have a small compilable test case, except a build tree from a
large project. But what happened was code like this

f()
{
   static void *addr[] = {
          &&label1,
          &&label2, 
          ..
   };
   /* labels defined in the code */
}

The LTO partitioner would put addr into a different ltrans unit than f.
But the assembler output of addr contains direct references to the code labels
in the assembler of f.

This results in lots of assembler errors for undefined labels.


             reply	other threads:[~2014-06-27 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 21:26 andi-gcc at firstfloor dot org [this message]
2014-06-27 23:04 ` [Bug lto/61635] " hubicka at gcc dot gnu.org
2014-06-28  1:16 ` andi at firstfloor dot org
2014-06-28  6:33 ` hubicka at ucw dot cz
2014-06-28 15:51 ` andi-gcc at firstfloor dot org
2014-06-28 15:57 ` andi-gcc at firstfloor dot org
2014-06-28 21:55 ` hubicka at ucw dot cz
2015-03-29 19:57 ` andi-gcc at firstfloor dot org
2015-03-30  7:09 ` hubicka at gcc dot gnu.org
2015-03-30  7:24 ` hubicka at ucw dot cz
2015-03-30  8:23 ` hubicka 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-61635-4@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).