public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105832] [13 Regression] Dead Code Elimination Regression at -O3 (trunk vs. 12.1.0)
Date: Tue, 20 Dec 2022 14:03:02 +0000 [thread overview]
Message-ID: <bug-105832-4-eXLf0maksC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105832-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105832
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Raising --param max-jump-thread-duplication-stmts from its default 15 to 17
fixes the issue. So the issue is slightly different accounting of sizes in the
threading code and slightly different IL (though it is smaller). Quite
possibly the bisection wasn't accurate.
next prev parent reply other threads:[~2022-12-20 14:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 9:59 [Bug tree-optimization/105832] New: " theodort at inf dot ethz.ch
2022-06-13 12:35 ` [Bug tree-optimization/105832] [13 Regression] " rguenth at gcc dot gnu.org
2022-06-14 11:14 ` rguenth at gcc dot gnu.org
2022-06-14 11:50 ` rguenth at gcc dot gnu.org
2022-12-20 14:03 ` rguenth at gcc dot gnu.org [this message]
2022-12-22 12:03 ` marxin at gcc dot gnu.org
2022-12-22 12:56 ` rguenth at gcc dot gnu.org
2022-12-22 14:48 ` marxin at gcc dot gnu.org
2023-02-21 14:27 ` rguenth at gcc dot gnu.org
2023-04-08 14:43 ` law at gcc dot gnu.org
2023-04-26 6:56 ` [Bug tree-optimization/105832] [13/14 " rguenth at gcc dot gnu.org
2023-07-12 18:00 ` pinskia at gcc dot gnu.org
2023-07-12 18:29 ` law at gcc dot gnu.org
2023-07-27 9:23 ` rguenth at gcc dot gnu.org
2023-08-07 8:40 ` pinskia at gcc dot gnu.org
2023-09-03 5:42 ` pinskia at gcc dot gnu.org
2023-09-03 6:31 ` pinskia at gcc dot gnu.org
2023-09-03 16:27 ` pinskia at gcc dot gnu.org
2023-09-05 20:57 ` cvs-commit at gcc dot gnu.org
2023-09-05 20:59 ` 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-105832-4-eXLf0maksC@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).