public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105643] [13 Regression] Code-Size regression for specrate 538.imagick_r
Date: Wed, 01 Jun 2022 07:50:45 +0000	[thread overview]
Message-ID: <bug-105643-4-uqpbxaTlib@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105643-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643

--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 31 May 2022, crazylht at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643
> 
> --- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
> Looks like codesize decreased after
> r13-754-ga1c9f779f75283427316b5c670c1e01ff8ce9ced.
> 
> Now we have cost model for unswitching loop
> 
> decorate.c:605:25: note: not unswitching condition, cost too big (37 insns
> copied to 35 and 37)

Yes, I noticed that when comparing opt-info before/after on SPEC as
well.  Note the actual cost limit wasn't adjusted in any way, there's
still some planned improvements pending and adjusting the cost limit
is one of that.

  parent reply	other threads:[~2022-06-01  7:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  9:06 [Bug tree-optimization/105643] New: " admin at levyhsu dot com
2022-05-18 10:03 ` [Bug tree-optimization/105643] " pinskia at gcc dot gnu.org
2022-05-18 12:47 ` rguenth at gcc dot gnu.org
2022-05-18 13:15 ` marxin at gcc dot gnu.org
2022-05-19  3:46 ` admin at levyhsu dot com
2022-05-19  8:51 ` admin at levyhsu dot com
2022-05-19  8:52 ` admin at levyhsu dot com
2022-05-19  9:11 ` admin at levyhsu dot com
2022-05-19 10:31 ` rguenth at gcc dot gnu.org
2022-05-31  3:56 ` crazylht at gmail dot com
2022-06-01  7:50 ` rguenther at suse dot de [this message]
2022-10-19 10: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=bug-105643-4-uqpbxaTlib@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).