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/109213] [13 Regression] -Os generates significantly more code since r13-723 Date: Mon, 27 Mar 2023 07:43:20 +0000 [thread overview] Message-ID: <bug-109213-4-P9Ix0VasZL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109213-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109213 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P2 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- So the gist is that IMHO inlining shouldn't regress when 40 <- 264 is changed to 0 <- 264 since the overall stack size is smaller and the absolute growth is the same. That's just counter-intuitive. This behavior isn't a recent regression, but the testcase regressed in 13 because of the extra variable elimination. For this reason making P2, a regression when that stack limit related behavior was introduced. Honza?
next prev parent reply other threads:[~2023-03-27 7:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-20 11:53 [Bug tree-optimization/109213] New: [13 Regression] -Os generates significantly more code theodort at inf dot ethz.ch 2023-03-20 13:07 ` [Bug tree-optimization/109213] " rguenth at gcc dot gnu.org 2023-03-20 17:36 ` pinskia at gcc dot gnu.org 2023-03-20 17:36 ` pinskia at gcc dot gnu.org 2023-03-20 17:39 ` pinskia at gcc dot gnu.org 2023-03-20 17:54 ` pinskia at gcc dot gnu.org 2023-03-21 8:45 ` [Bug tree-optimization/109213] [13 Regression] -Os generates significantly more code since r13-723 jakub at gcc dot gnu.org 2023-03-21 13:37 ` rguenth at gcc dot gnu.org 2023-03-27 7:43 ` rguenth at gcc dot gnu.org [this message] 2023-03-29 15:04 ` hubicka at gcc dot gnu.org 2023-04-26 6:58 ` [Bug tree-optimization/109213] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-21 9:14 ` [Bug tree-optimization/109213] [13/14/15 " jakub 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-109213-4-P9Ix0VasZL@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).