public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeevitha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110606] ICE output_operand: '%&' used without any local dynamic TLS references on powerpc64le-linux-gnu
Date: Tue, 05 Dec 2023 16:21:25 +0000 [thread overview]
Message-ID: <bug-110606-4-3JH1C69r7N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110606-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
--- Comment #7 from Jeevitha <jeevitha at gcc dot gnu.org> ---
The following insns are dead at sched2, but not removed until pass_final, If
these instruction are removed there will be no ICE.
(insn 80 110 111 3 (set (reg:DI 28 28 [145])
(high:DI (unspec:DI [
(reg:DI 2 2)
] UNSPEC_TLSLD))) "test.cc":27:7 737 {*tls_ld_high64}
(expr_list:REG_EQUIV (high:DI (unspec:DI [
(reg:DI 2 2)
] UNSPEC_TLSLD))
(nil)))
(insn:TI 81 106 54 3 (set (reg:DI 28 28 [139])
(lo_sum:DI (reg:DI 28 28 [145])
(unspec:DI [
(reg:DI 2 2)
] UNSPEC_TLSLD))) "test.cc":27:7 738 {*tls_ld_low64}
(expr_list:REG_DEAD (reg:DI 2 2)
(nil)))
(insn 72 23 53 4 (set (reg:DI 3 3)
(reg:DI 28 28 [139])) "test.cc":27:7 683 {*movdi_internal64}
(nil))
call_insn/u 26 53 35 4 (parallel [
(set (reg:DI 3 3)
(call (mem:SI (symbol_ref:DI ("__tls_get_addr") [flags 0x41]
<function_decl 0x7ffff576df00 __tls_get_addr>) [0 S4 A8])
(unspec:DI [
(reg:DI 2 2)
] UNSPEC_TLSLD)))
(use (const_int 0 [0]))
(clobber (reg:DI 96 lr))
]) "test.cc":27:7 776 {*call_value_nonlocal_aixdi}
(expr_list:REG_UNUSED (reg:DI 3 3)
(expr_list:REG_CALL_DECL (symbol_ref:DI ("__tls_get_addr") [flags 0x41]
<function_decl 0x7ffff576df00 __tls_get_addr>)
(expr_list:REG_EH_REGION (const_int -2147483648
[0xffffffff80000000])
(nil))))
(expr_list (use (reg:DI 2 2))
(expr_list (use (reg:DI 3 3))
(nil))))
next prev parent reply other threads:[~2023-12-05 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 15:07 [Bug target/110606] New: [10/11/12/13/14] " doko at gcc dot gnu.org
2023-07-10 6:42 ` [Bug target/110606] " rguenth at gcc dot gnu.org
2023-07-19 9:14 ` marcus at mc dot pp.se
2023-11-17 3:54 ` bergner at gcc dot gnu.org
2023-11-28 15:32 ` segher at gcc dot gnu.org
2023-11-28 15:43 ` segher at gcc dot gnu.org
2023-12-04 9:36 ` jeevitha at gcc dot gnu.org
2023-12-05 16:21 ` jeevitha at gcc dot gnu.org [this message]
2023-12-05 17:26 ` segher at gcc dot gnu.org
2023-12-05 18:26 ` jeevitha at gcc dot gnu.org
2023-12-11 4:57 ` jeevitha at gcc dot gnu.org
2023-12-14 7:45 ` jeevitha 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-110606-4-3JH1C69r7N@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).