public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/106399] [10/11/12/13 Regression] Wrong debug info for function with nested function under O0 Date: Fri, 22 Jul 2022 07:19:34 +0000 [thread overview] Message-ID: <bug-106399-4-NtKmsJBM79@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106399-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106399 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.4.0, 11.3.0, 12.1.0, | |9.5.0 Last reconfirmed| |2022-07-22 Summary|Wrong debug info for |[10/11/12/13 Regression] |function with nested |Wrong debug info for |function under O0 |function with nested | |function under O0 Target Milestone|--- |10.5 Ever confirmed|0 |1 Known to work| |7.5.0, 8.4.0 Keywords| |needs-bisection, | |wrong-debug Priority|P3 |P2 Status|UNCONFIRMED |NEW --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. It works with -O -fno-inline, it also worked at some point.
next prev parent reply other threads:[~2022-07-22 7:19 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-22 5:33 [Bug debug/106399] New: " liyd2021 at gmail dot com 2022-07-22 7:19 ` rguenth at gcc dot gnu.org [this message] 2022-07-22 10:10 ` [Bug debug/106399] [10/11/12/13 Regression] Wrong debug info for function with nested function under O0 since r9-1284-gd70ba0c10dec6968 marxin at gcc dot gnu.org 2022-07-22 12:31 ` ebotcazou at gcc dot gnu.org 2022-07-28 17:47 ` jakub at gcc dot gnu.org 2022-07-29 8:44 ` ebotcazou at gcc dot gnu.org 2022-07-29 8:45 ` ebotcazou at gcc dot gnu.org 2023-07-07 10:43 ` [Bug debug/106399] [11/12/13/14 " 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-106399-4-NtKmsJBM79@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).