public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/47259] [4.7 Regression] LTO and global register variable
Date: Fri, 02 Dec 2011 12:15:00 -0000	[thread overview]
Message-ID: <bug-47259-4-9yufgiBgtS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47259-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #11 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-12-02 12:14:29 UTC ---
This must be a new bug, the testcase passed previously, the register name
(esi) is rejected at link-time only.

#1  0x0000000000d4dbba in make_decl_rtl (decl=0x7ffff5a2c140)
    at /space/rguenther/src/svn/trunk/gcc/varasm.c:1207
1207            error ("invalid register name for %q+D", decl);
(gdb) l
1202          reg_number = decode_reg_name (asmspec);
1203          /* First detect errors in declaring global registers.  */
1204          if (reg_number == -1)
1205            error ("register name not specified for %q+D", decl);
1206          else if (reg_number < 0)
1207            error ("invalid register name for %q+D", decl);
(gdb) p asmspec
$2 = 0x7ffff5b58401 "esi.2318"

we mangle the register name now.  That's of course bogus.  It seems we
put the global register vars into the alias machinery now?  Honza?


  parent reply	other threads:[~2011-12-02 12:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 19:32 [Bug lto/47259] New: " d.g.gorbachev at gmail dot com
2011-01-11 20:10 ` [Bug lto/47259] " d.g.gorbachev at gmail dot com
2011-01-12 11:22 ` rguenth at gcc dot gnu.org
2011-01-12 13:38 ` rguenth at gcc dot gnu.org
2011-01-12 13:38 ` d.g.gorbachev at gmail dot com
2011-01-12 14:21 ` rguenth at gcc dot gnu.org
2011-01-12 15:14 ` rguenth at gcc dot gnu.org
2011-01-12 15:22 ` rguenth at gcc dot gnu.org
2011-01-12 15:47 ` rguenth at gcc dot gnu.org
2011-12-02 11:12 ` ubizjak at gmail dot com
2011-12-02 11:25 ` [Bug lto/47259] [4.7 Regression] " ubizjak at gmail dot com
2011-12-02 12:15 ` rguenth at gcc dot gnu.org [this message]
2011-12-02 15:50 ` rguenth at gcc dot gnu.org
2011-12-05  9:30 ` 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-47259-4-9yufgiBgtS@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).