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/101936] [12 Regression] 538.imagick_r -Ofast regression on Kabylake since g:872da9a6f664a06d73c987aa0cb2e5b830158a10
Date: Mon, 23 Aug 2021 09:47:37 +0000 [thread overview]
Message-ID: <bug-101936-4-O1KIFL8fKy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101936-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101936
--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Martin Liška from comment #5)
> > https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=32.507.0
> >
>
> Looking at LNT, the benchmark score is not back after the reversion of the
> patch.
> Maybe we face now PR101935?
probably.
next prev parent reply other threads:[~2021-08-23 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:48 [Bug tree-optimization/101936] New: 538.imagick_r -Ofast regression Kabylake marxin at gcc dot gnu.org
2021-08-16 12:49 ` [Bug tree-optimization/101936] [12 Regression] " marxin at gcc dot gnu.org
2021-08-16 13:27 ` [Bug tree-optimization/101936] [12 Regression] 538.imagick_r -Ofast regression on Kabylake since g:872da9a6f664a06d73c987aa0cb2e5b830158a10 marxin at gcc dot gnu.org
2021-08-17 1:56 ` [Bug target/101936] " crazylht at gmail dot com
2021-08-17 8:08 ` crazylht at gmail dot com
2021-08-19 2:29 ` cvs-commit at gcc dot gnu.org
2021-08-23 9:02 ` marxin at gcc dot gnu.org
2021-08-23 9:47 ` crazylht at gmail dot com [this message]
2021-09-15 15:58 ` marxin 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-101936-4-O1KIFL8fKy@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).