public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61192] Conflict between register and function name for lto on sparc
Date: Fri, 24 Dec 2021 10:32:32 +0000	[thread overview]
Message-ID: <bug-61192-4-3ZKosqsFFN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61192-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-12-24
      Known to fail|                            |9.1.0
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
           Keywords|lto                         |ice-checking,
                   |                            |ice-on-valid-code
          Component|lto                         |middle-end

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed here is a testcase for x86_64:
register int hh __asm__("r14");
int jj;

__getreent() {
  int cpu_self = hh;
  jj = cpu_self;
}
int r14() {}

----- CUT ----
Here is the ICE we get on the trunk (and all the way down to GCC 9, GCC 8 does
not to ICE with -fchecking):

<source>:9:1: error: assembler name hash list corrupted
    9 | int r14() {}
      | ^~~
*r14/0 (hh) @0x7f0e412d1000
  Type: variable definition analyzed
  Visibility: force_output semantic_interposition no_reorder public
  References: 
  Referring: __getreent/2 (read) 
  Availability: not-ready
  Varpool flags:
<source>:9:1: internal compiler error: symtab_node::verify failed
0x1e454c9 internal_error(char const*, ...)
        ???:0
0x900b69 symtab_node::verify()
        ???:0
0x9020e7 symtab_node::verify_symtab_nodes()
        ???:0
0x91e9bf symbol_table::finalize_compilation_unit()
        ???:0
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1

  parent reply	other threads:[~2021-12-24 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  9:53 [Bug lto/61192] New: " cederman at gaisler dot com
2014-05-15 10:05 ` [Bug lto/61192] " rguenth at gcc dot gnu.org
2014-10-20 11:24 ` i.palachev at samsung dot com
2014-10-20 14:48 ` cederman at gaisler dot com
2021-12-24 10:32 ` pinskia at gcc dot gnu.org [this message]
2021-12-24 10:34 ` [Bug middle-end/61192] Conflict between global register and function name pinskia at gcc dot gnu.org
2023-10-18 18:54 ` pinskia at gcc dot gnu.org
2023-10-18 18:55 ` pinskia 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-61192-4-3ZKosqsFFN@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).