public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110067] [14 Regression] Wrong code on pixman-0.42.2
Date: Wed, 31 May 2023 23:28:14 +0000 [thread overview]
Message-ID: <bug-110067-4-8b5ZEJ2PTZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110067-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110067
Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #2 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I am suspecting it was caused by r14-1402-gd8545fb2c71683f407bfd9670 .
I did not bisect and tested only a revert on top of r14-1423-gfefa7db2c31fee.
The revert does indeed restore pixman-0.42.2 test suite passing!
next prev parent reply other threads:[~2023-05-31 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 22:42 [Bug tree-optimization/110067] New: " slyfox at gcc dot gnu.org
2023-05-31 22:46 ` [Bug tree-optimization/110067] " pinskia at gcc dot gnu.org
2023-05-31 23:28 ` slyfox at gcc dot gnu.org [this message]
2023-06-01 1:42 ` crazylht at gmail dot com
2023-06-01 1:55 ` crazylht at gmail dot com
2023-06-01 1:55 ` crazylht at gmail dot com
2023-06-01 9:46 ` slyfox at gcc dot gnu.org
2023-06-02 7:38 ` rguenth at gcc dot gnu.org
2023-06-02 7:55 ` crazylht at gmail dot com
2023-06-03 0:09 ` cvs-commit at gcc dot gnu.org
2023-06-03 0:10 ` crazylht at gmail dot com
2023-06-03 7:33 ` slyfox at gcc dot gnu.org
2023-06-04 5:08 ` sjames at gcc dot gnu.org
2023-06-05 1:01 ` crazylht at gmail dot com
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-110067-4-8b5ZEJ2PTZ@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).