public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "assaiante at diag dot uniroma1.it" <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: Thu, 17 Feb 2022 13:48:28 +0000 [thread overview] Message-ID: <bug-104549-4-MQWd4xVzh9@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 --- Comment #4 from Cristian Assaiante <assaiante at diag dot uniroma1.it> --- We have tested also multiple versions of gdb. With versions 9.2 and 11.2 we have the same behavior: variable i is visible for gcc4 and gcc7 and not visible for more recent gcc versions. With version 10.2 we have that variable i is marked as optimized out for gcc4 and gcc7 and not visible for more recent gcc versions.
prev parent reply other threads:[~2022-02-17 13:48 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 ` [Bug debug/104549] " jakub at gcc dot gnu.org 2022-02-16 13:01 ` 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 [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-104549-4-MQWd4xVzh9@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).