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 debug/105261] schedule-insns2 and ipa-sra make alive constant variables not available Date: Mon, 07 Nov 2022 05:05:11 +0000 [thread overview] Message-ID: <bug-105261-4-zlyR69U4cP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105261-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105261 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The IPA-SRA issue seems to be fixed on the trunk. That is in the optimized dump we now have: # DEBUG BEGIN_STMT # DEBUG INLINE_ENTRY b # DEBUG BEGIN_STMT # DEBUG l_5 => 0 # DEBUG l_54 => 5 # DEBUG l_362 => 4 # DEBUG BEGIN_STMT # DEBUG l_53 => 4 # DEBUG l_55 => 0 While in GCC 12 we did not have that. The scheduler issue I have not looked into at all since it is harder to figure out RTL level debug info really.
prev parent reply other threads:[~2022-11-07 5:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 11:28 [Bug debug/105261] New: " assaiante at diag dot uniroma1.it 2022-04-13 13:34 ` [Bug debug/105261] " assaiante at diag dot uniroma1.it 2022-11-07 5:05 ` pinskia at gcc dot gnu.org [this message]
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-105261-4-zlyR69U4cP@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).