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 debug/78685] -Og generates too many "<optimized out>"s Date: Wed, 28 Feb 2024 07:47:15 +0000 [thread overview] Message-ID: <bug-78685-4-iEhJ58dxzz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-78685-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lukas.graetz@tu-darmstadt.d | |e --- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 114144 has been marked as a duplicate of this bug. ***
prev parent reply other threads:[~2024-02-28 7:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-78685-4@http.gcc.gnu.org/bugzilla/> 2021-05-18 13:36 ` egallager at gcc dot gnu.org 2021-05-18 15:35 ` rsandifo at gcc dot gnu.org 2021-12-13 13:38 ` mark at hotpy dot org 2023-10-09 9:17 ` rguenth at gcc dot gnu.org 2024-02-28 7:47 ` 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-78685-4-iEhJ58dxzz@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).