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/104549] Missing variable at O2/O3 likely caused by -fearly-inlining Date: Tue, 15 Feb 2022 17:30:37 +0000 [thread overview] Message-ID: <bug-104549-4-upA1Dvjr1Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104549 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I don't understand what problem you complain about. The i variable is certainly in the debug info: .uleb128 0xc # (DIE (0xa4) DW_TAG_variable) .ascii "i\0" # DW_AT_name .byte 0x1 # DW_AT_decl_file (pr104549.c) .byte 0x3 # DW_AT_decl_line .byte 0x9 # DW_AT_decl_column .long 0x3c # DW_AT_type and has the correct value: .uleb128 0x2 # (DIE (0x7e) DW_TAG_variable) .long 0xa4 # DW_AT_abstract_origin # DW_AT_const_value (0)
next prev parent reply other threads:[~2022-02-15 17:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 15:46 [Bug debug/104549] New: " assaiante at diag dot uniroma1.it 2022-02-15 17:30 ` jakub at gcc dot gnu.org [this message] 2022-02-16 13:01 ` [Bug debug/104549] " jakub at gcc dot gnu.org 2022-02-17 12:38 ` assaiante at diag dot uniroma1.it 2022-02-17 13:48 ` 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-104549-4-upA1Dvjr1Z@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).