public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher 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 17:26:46 +0000 [thread overview] Message-ID: <bug-110606-4-4FT99H0tew@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 #8 from Segher Boessenkool <segher at gcc dot gnu.org> --- What does "dead at sched2" mean? Are they dead when sched2 starts, or made dead by it? Well it must be the former; what pass does make it dead, then? split3 apparently? Why is this not done in split2 already, any good reason?
next prev parent reply other threads:[~2023-12-05 17:26 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 2023-12-05 17:26 ` segher at gcc dot gnu.org [this message] 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-4FT99H0tew@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: linkBe 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).