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/47590] pragma optimize doesn't recompute derived options (was: var tracking produces wrong debug in code where optimization is turned off using pragma) Date: Sat, 01 Jan 2022 07:44:12 +0000 [thread overview] Message-ID: <bug-47590-4-jURVTRfHt8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47590-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47590 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-debug Component|debug |middle-end --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I wonder if this has been fixed since there has been so many fixes for #prama optimize even in GCC 4.8.0.
prev parent reply other threads:[~2022-01-01 7:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-02 16:06 [Bug debug/47590] New: var tracking produces wrong debug in code where optimization is turned off using pragma hariharans at picochip dot com 2011-02-02 16:08 ` [Bug debug/47590] " hariharans at picochip dot com 2011-02-02 16:09 ` hariharans at picochip dot com 2011-03-27 14:31 ` aoliva at gcc dot gnu.org 2011-03-27 14:36 ` aoliva at gcc dot gnu.org 2011-06-03 1:42 ` aoliva at gcc dot gnu.org 2011-06-04 10:16 ` aoliva at gcc dot gnu.org 2011-06-04 10:22 ` aoliva at gcc dot gnu.org 2011-11-10 16:40 ` hariharans at picochip dot com 2012-03-25 11:56 ` [Bug debug/47590] pragma optimize doesn't recompute derived options (was: var tracking produces wrong debug in code where optimization is turned off using pragma) aoliva at gcc dot gnu.org 2022-01-01 7:44 ` 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-47590-4-jURVTRfHt8@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).