public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104686] [12 Regression] Huge compile-time regression building SPEC 2017 538.imagick_r with -march=skylake
Date: Mon, 28 Feb 2022 01:19:07 +0000 [thread overview]
Message-ID: <bug-104686-4-lQB2VMZaz0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104686-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104686
--- Comment #11 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Martin Liška from comment #8)
> (In reply to Martin Liška from comment #7)
> > (In reply to Richard Biener from comment #6)
> > > Both revisions affect vectorizer cost modeling only. With
> > > -fno-vect-cost-model it compiles faster for me but still a slow 30s and 91%
> > > in RA.
> >
> > There are numbers with -fno-vect-cost-model:
> >
> > Bisecting latest revisions
> > a9e2ebe839d56416(24 Feb 2022 22:16)(oliva@adacore.com): [took: 36.06 s]
> > result: OK
> > 250f234988b62316(20 Apr 2021 09:51)(stefansf@linux.ibm.com): [took: 18.35
> > s] result: OK
> >
> > I'm going to find out where the change happensed.
>
> Which started with r12-2463-ga6291d88d5b6c17d.
Wonder if it's related to hard register usage in pass_expand
op1 = ix86_gen_scratch_sse_rtx (mode);
next prev parent reply other threads:[~2022-02-28 1:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 12:05 [Bug target/104686] New: " rguenth at gcc dot gnu.org
2022-02-25 12:06 ` [Bug target/104686] " rguenth at gcc dot gnu.org
2022-02-25 12:07 ` rguenth at gcc dot gnu.org
2022-02-25 12:13 ` rguenth at gcc dot gnu.org
2022-02-25 12:23 ` marxin at gcc dot gnu.org
2022-02-25 12:23 ` marxin at gcc dot gnu.org
2022-02-25 12:29 ` marxin at gcc dot gnu.org
2022-02-25 12:36 ` rguenth at gcc dot gnu.org
2022-02-25 12:38 ` marxin at gcc dot gnu.org
2022-02-25 12:47 ` marxin at gcc dot gnu.org
2022-02-25 13:00 ` rguenth at gcc dot gnu.org
2022-02-25 13:17 ` rguenth at gcc dot gnu.org
2022-02-28 1:19 ` crazylht at gmail dot com [this message]
2022-02-28 1:48 ` crazylht at gmail dot com
2022-02-28 7:03 ` cvs-commit at gcc dot gnu.org
2022-02-28 7:03 ` rguenth at gcc dot gnu.org
2022-03-01 9:20 ` rguenth at gcc dot gnu.org
2022-03-01 15:45 ` rguenth at gcc dot gnu.org
2022-03-01 15:54 ` rguenth at gcc dot gnu.org
2022-03-01 16:40 ` rguenth at gcc dot gnu.org
2022-03-01 21:58 ` vmakarov at gcc dot gnu.org
2022-03-02 8:08 ` rguenth at gcc dot gnu.org
2022-03-02 14:09 ` cvs-commit at gcc dot gnu.org
2022-03-02 14:10 ` 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-104686-4-lQB2VMZaz0@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).