public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103734] New: IPA-CP opportunity for imagick in SPECCPU 2017
Date: Wed, 15 Dec 2021 12:14:02 +0000	[thread overview]
Message-ID: <bug-103734-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103734
           Summary: IPA-CP opportunity for imagick in SPECCPU 2017
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tnfchris at gcc dot gnu.org
                CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

When using --param ipa-cp-eval-threshold=1 --param ipa-cp-unit-growth=20 on
imagick the hot functions MorphologyApply and GetVirtualPixelsFromNexus get
replaced by specialized versions that are much smaller and faster.

Some other benchmarks like leela also get very small uplifts but the imagick
one is worth 14%.  Both flags seem to be needed.

             reply	other threads:[~2021-12-15 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 12:14 tnfchris at gcc dot gnu.org [this message]
2021-12-15 12:22 ` [Bug ipa/103734] " marxin at gcc dot gnu.org
2021-12-15 12:50 ` hubicka at kam dot mff.cuni.cz
2021-12-16  6:18 ` pinskia at gcc dot gnu.org
2021-12-16  6:37 ` crazylht at gmail dot com
2021-12-17 17:23 ` pthaugen 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-103734-4@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).