public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug tree-optimization/102446] [9/10/11/12 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 22 Sep 2021 12:56:30 +0200 [thread overview]
Message-ID: <20210922105630.GC85450@kam.mff.cuni.cz> (raw)
In-Reply-To: <bug-102446-4-GyGfhIy9bX@http.gcc.gnu.org/bugzilla/>
> Started with r5-6477-g3620b606822f80863488ca4883542d848d41f9f9
This only affects early inlining decisions, so it may be useful to
bisect this with --param early-inlining-insns=14
Honza
next prev parent reply other threads:[~2021-09-22 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 9:00 [Bug tree-optimization/102446] New: " zhendong.su at inf dot ethz.ch
2021-09-22 10:50 ` [Bug tree-optimization/102446] " rguenth at gcc dot gnu.org
2021-09-22 10:54 ` [Bug tree-optimization/102446] [9/10/11/12 Regression] " jakub at gcc dot gnu.org
2021-09-22 10:56 ` Jan Hubicka [this message]
2021-09-22 10:56 ` rguenth at gcc dot gnu.org
2021-09-22 10:56 ` hubicka at ucw dot cz
2021-09-22 10:57 ` [Bug rtl-optimization/102446] " rguenth at gcc dot gnu.org
2021-09-22 10:57 ` rguenth at gcc dot gnu.org
2021-09-22 11:01 ` jakub at gcc dot gnu.org
2021-09-22 11:02 ` jakub at gcc dot gnu.org
2021-09-22 11:11 ` pinskia at gcc dot gnu.org
2021-09-22 11:29 ` jakub at gcc dot gnu.org
2022-01-30 2:04 ` pinskia at gcc dot gnu.org
2022-01-30 12:34 ` jakub at gcc dot gnu.org
2022-01-30 20:48 ` pinskia at gcc dot gnu.org
2022-05-27 9:46 ` [Bug rtl-optimization/102446] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2022-07-29 12:22 ` [Bug rtl-optimization/102446] [10/11 " rguenth at gcc dot gnu.org
2022-07-29 12:44 ` jakub at gcc dot gnu.org
2022-07-29 12:45 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug rtl-optimization/102446] [11 " 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=20210922105630.GC85450@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).