public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109566] powerpc: unrecognizable insn for -mcpu=e6500
Date: Fri, 21 Apr 2023 08:54:06 +0000 [thread overview]
Message-ID: <bug-109566-4-0DTA9F2Bll@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109566-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #2 from Sebastian Huber <sebastian.huber@embedded-brains.de> ---
Sorry for the confusion, the actual bad commit was the follow up commit (NOT
d75be7e4343f049176546aa9517d570e5eb67954):
commit 6cc3394507a2303a18891d34222c53f679256c37
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Wed Oct 5 10:42:07 2022 -0400
propagate partial equivs in the cache.
Adjust on-entry cache propagation to look for and propagate both full
and partial equivalences.
gcc/
PR tree-optimization/102540
PR tree-optimization/102872
* gimple-range-cache.cc (ranger_cache::fill_block_cache):
Handle partial equivs.
(ranger_cache::range_from_dom): Cleanup dump output.
gcc/testsuite/
* gcc.dg/pr102540.c: New.
* gcc.dg/pr102872.c: New.
next prev parent reply other threads:[~2023-04-21 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 8:34 [Bug target/109566] New: " sebastian.huber@embedded-brains.de
2023-04-21 8:34 ` [Bug target/109566] " sebastian.huber@embedded-brains.de
2023-04-21 8:54 ` sebastian.huber@embedded-brains.de [this message]
2023-04-24 6:31 ` [Bug target/109566] powerpc: unrecognizable insn for -mcpu=e6500, -mcpu=power3, ..., -mcpu=power10 sebastian.huber@embedded-brains.de
2023-04-24 6:33 ` sebastian.huber@embedded-brains.de
2023-04-24 8:27 ` [Bug target/109566] [13/14 Regression] " rguenth at gcc dot gnu.org
2023-04-24 8:51 ` jakub at gcc dot gnu.org
2023-04-24 9:09 ` sebastian.huber@embedded-brains.de
2023-04-24 9:32 ` jakub at gcc dot gnu.org
2023-04-24 9:50 ` jakub at gcc dot gnu.org
2023-04-24 10:09 ` jakub at gcc dot gnu.org
2023-04-24 10:33 ` jakub at gcc dot gnu.org
2023-04-24 10:37 ` jakub at gcc dot gnu.org
2023-04-24 10:54 ` [Bug target/109566] [12/13/14 " jakub at gcc dot gnu.org
2023-04-24 10:57 ` jakub at gcc dot gnu.org
2023-04-24 11:03 ` sebastian.huber@embedded-brains.de
2023-04-25 12:21 ` cvs-commit at gcc dot gnu.org
2023-04-25 12:24 ` segher at gcc dot gnu.org
2023-04-25 12:37 ` cvs-commit at gcc dot gnu.org
2023-04-25 14:12 ` [Bug target/109566] [12 " jakub at gcc dot gnu.org
2023-04-25 14:12 ` jakub at gcc dot gnu.org
2023-04-26 10:59 ` cvs-commit at gcc dot gnu.org
2023-04-26 11:00 ` jakub 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-109566-4-0DTA9F2Bll@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).