public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94123] [10 regression] r10-1734, SVN r273240, causes gcc.target/powerpc/pr87507.c to fail
Date: Wed, 01 Apr 2020 19:24:40 +0000 [thread overview]
Message-ID: <bug-94123-4-s166TSfHGC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94123-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94123
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:7546463b9f7a0b001cf61a94dcfc18f540721390
commit r10-7501-g7546463b9f7a0b001cf61a94dcfc18f540721390
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Wed Apr 1 14:24:07 2020 -0500
subreg: Fix PR94123, SVN r273240 causes gcc.target/powerpc/pr87507.c to
fail
Segher's patch that added -fsplit-wide-types-early and enabled by default
for rs6000, caused pr87507.c to FAIL because when running lower-subreg
earlier, we don't see any pseudo-to-pseudo copies of our wide type,
which are created by combine, therefore, we skip decomposing our TImode
accesses. The fix here is just to always run the third pass of
lower-subreg
instead of disabling it if we ran the second pass.
2020-04-01 Peter Bergner <bergner@linux.ibm.com>
PR rtl-optimization/94123
* lower-subreg.c (pass_lower_subreg3::gate): Remove test for
flag_split_wide_types_early.
next prev parent reply other threads:[~2020-04-01 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 14:53 [Bug target/94123] New: [10 regression] r10-7093 " seurer at gcc dot gnu.org
2020-03-10 14:57 ` [Bug target/94123] " seurer at gcc dot gnu.org
2020-03-10 16:47 ` jakub at gcc dot gnu.org
2020-03-10 18:13 ` seurer at gcc dot gnu.org
2020-03-11 7:38 ` rguenth at gcc dot gnu.org
2020-03-11 15:54 ` [Bug target/94123] [10 regression] r10-1734, SVN r273240, " seurer at gcc dot gnu.org
2020-03-11 19:44 ` segher at gcc dot gnu.org
2020-03-20 11:44 ` rguenth at gcc dot gnu.org
2020-03-20 14:13 ` bergner at gcc dot gnu.org
2020-03-20 14:20 ` rguenth at gcc dot gnu.org
2020-03-24 18:48 ` bergner at gcc dot gnu.org
2020-03-25 7:22 ` rguenth at gcc dot gnu.org
2020-03-27 22:48 ` bergner at gcc dot gnu.org
2020-04-01 19:24 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-01 19:27 ` bergner 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-94123-4-s166TSfHGC@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).