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 tree-optimization/85509] fails to promote local static to const Date: Mon, 30 Aug 2021 05:28:30 +0000 [thread overview] Message-ID: <bug-85509-4-CPL5bY3x9n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85509-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85509 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- For some reason CCP1 is not able to do it but CCP2 can; though CCP2 is after inlining so IPA so nothing is done with respect to inlining and such. CCP1 dump: Visiting statement: # VUSE <.MEM_13> PerformSafely.3_3 = _ZZL7RunTestvE13PerformSafelyD.2380; which is likely CONSTANT Lattice value changed to VARYING. Adding SSA edges to worklist. CCP2 dump: Visiting statement: # VUSE <.MEM_8> # PT = nonlocal escaped null PerformSafely.2_2 = _ZZ7RunTestvE13PerformSafelyD.2379; which is likely CONSTANT Lattice value changed to CONSTANT _Z7PerformIL_ZL9SumSafelyRiRKiEEbS0_S2_D.2380. Adding SSA edges to worklist. marking stmt to be not simulated again
next parent reply other threads:[~2021-08-30 5:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85509-4@http.gcc.gnu.org/bugzilla/> 2021-08-30 5:28 ` pinskia at gcc dot gnu.org [this message] 2021-08-30 7:49 ` [Bug ipa/85509] " 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-85509-4-CPL5bY3x9n@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).