public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager 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: Tue, 18 May 2021 13:36:50 +0000 [thread overview]
Message-ID: <bug-78685-4-S0Q5tO5skF@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
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org,
| |fredrik at dolda2000 dot com,
| |john.carter at taitradio dot com,
| |marxin at gcc dot gnu.org,
| |philipp.lucas at siemens dot com,
| |yuxian.chen at intel dot com
--- Comment #19 from Eric Gallager <egallager at gcc dot gnu.org> ---
This bug came up on the gcc-help mailing list here:
https://gcc.gnu.org/pipermail/gcc-help/2021-May/140304.html
...and, while I'm here, let me update a few things...
(In reply to rsandifo@gcc.gnu.org from comment #18)
> (In reply to Eric Gallager from comment #17)
> > Richard Sandiford had a series of patches radically overhauling how -Og
> > works in general that might affect this bug:
> > https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01392.html
> > cc-ing him so he can comment on if it does in fact affect this bug.
>
> Yeah, part 2 of the series fixes this PR:
> https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01394.html
Has this series been merged yet? Or at least pinged recently?
(also, I'm redoing some CCs that seem to have been accidentally removed from
the CC list without showing up in the bug history as having been removed;
presumably this was from the server migration...)
next parent reply other threads:[~2021-05-18 13:36 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 [this message]
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
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-S0Q5tO5skF@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: link
Be 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).