public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/105108] incomplete/incorrect DWARF information at -O1 and -Og after inlining a function returning a constant Date: Thu, 31 Mar 2022 09:25:24 +0000 [thread overview] Message-ID: <bug-105108-4-BTl2f1FZfJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105108-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105108 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- And I certainly can't reproduce the wrong-debug issue you're talking about. If I change it to char l_144 = 8; then optimized dump has: <bb 2> [local count: 1073741824]: # DEBUG BEGIN_STMT # DEBUG l_144 => 8 # DEBUG BEGIN_STMT # DEBUG l_165 => 128 # DEBUG BEGIN_STMT # DEBUG l_144 => NULL # DEBUG BEGIN_STMT a = 1; return 0; and in the debugger it correctly says that (gdb) p l_144 $1 = <optimized out> because at the a = 1 store the value is unknown.
next prev parent reply other threads:[~2022-03-31 9:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-30 14:38 [Bug debug/105108] New: " assaiante at diag dot uniroma1.it 2022-03-31 6:39 ` [Bug debug/105108] " rguenth at gcc dot gnu.org 2022-03-31 9:20 ` jakub at gcc dot gnu.org 2022-03-31 9:25 ` jakub at gcc dot gnu.org [this message] 2022-03-31 10:20 ` rguenth at gcc dot gnu.org 2022-03-31 10:32 ` jakub at gcc dot gnu.org 2022-03-31 10:36 ` jakub at gcc dot gnu.org 2022-03-31 10:41 ` jakub at gcc dot gnu.org 2022-03-31 16:55 ` assaiante at diag dot uniroma1.it 2022-03-31 16:55 ` assaiante at diag dot uniroma1.it
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-105108-4-BTl2f1FZfJ@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).