public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103989] [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og since r12-1992-g6feb628a706e86eb
Date: Tue, 18 Jan 2022 14:43:26 +0000 [thread overview]
Message-ID: <bug-103989-4-bgvkNGebdx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103989-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103989
--- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:c952126870c92cf293d59ffb1497e402eb8fc269
commit r12-6677-gc952126870c92cf293d59ffb1497e402eb8fc269
Author: Richard Biener <rguenther@suse.de>
Date: Tue Jan 18 13:48:34 2022 +0100
ipa/103989 - avoid IPA inlining of small functions with -Og
The following change avoids doing IPA inlining of small functions
into functions compiled with -Og - those functions will see almost no
followup scalar cleanups so that the benefit anticipated by the
inliner will not be realized and instead the late diagnostic code
will be confused by dead code that is left around.
2022-01-18 Richard Biener <rguenther@suse.de>
PR ipa/103989
* ipa-inline.cc (inline_small_functions): Do not enqueue call
edges originating in functions compiled with -Og.
* g++.dg/opt/pr103989.C: New testcase.
next prev parent reply other threads:[~2022-01-18 14:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 12:10 [Bug tree-optimization/103989] New: [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og marc@nieper-wisskirchen.de
2022-01-12 12:16 ` [Bug tree-optimization/103989] [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og since r12-1992-g6feb628a706e86eb marxin at gcc dot gnu.org
2022-01-12 12:54 ` rguenth at gcc dot gnu.org
2022-01-12 17:44 ` jakub at gcc dot gnu.org
2022-01-12 19:11 ` pinskia at gcc dot gnu.org
2022-01-13 11:10 ` jakub at gcc dot gnu.org
2022-01-13 11:39 ` rguenth at gcc dot gnu.org
2022-01-13 11:56 ` Jan Hubicka
2022-01-13 11:56 ` hubicka at kam dot mff.cuni.cz
2022-01-13 12:03 ` Jan Hubicka
2022-01-13 12:03 ` hubicka at kam dot mff.cuni.cz
2022-01-13 12:25 ` rguenth at gcc dot gnu.org
2022-01-13 13:39 ` hubicka at kam dot mff.cuni.cz
2022-01-13 13:44 ` rguenther at suse dot de
2022-01-13 13:55 ` hubicka at kam dot mff.cuni.cz
2022-01-13 13:58 ` rguenth at gcc dot gnu.org
2022-01-13 14:11 ` Jan Hubicka
2022-01-13 14:11 ` hubicka at kam dot mff.cuni.cz
2022-01-13 15:01 ` cvs-commit at gcc dot gnu.org
2022-01-13 15:05 ` jakub at gcc dot gnu.org
2022-01-13 15:10 ` rguenther at suse dot de
2022-01-18 12:35 ` rguenth at gcc dot gnu.org
2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org
2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-18 14:43 ` rguenth 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-103989-4-bgvkNGebdx@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).