From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>,
Richard Biener <rguenther@suse.de>,
Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix out-of-ssa with unsupported vector types (PR rtl-optimization/90756)
Date: Wed, 03 Jul 2019 23:12:00 -0000 [thread overview]
Message-ID: <9ca8f69a-41b6-804f-6955-6e4046160c6b@redhat.com> (raw)
In-Reply-To: <20190703075941.GU815@tucnak>
On 7/3/19 1:59 AM, Jakub Jelinek wrote:
> Hi!
>
> This weird hink has been added by Alex in r228175, it isn't clear why
> nor how it ever can be correct. While say for DECL_MODE we have the problem
> that for global vars when switching between functions with different ISA
> selections the mode might not be ok, TYPE_MODE is stored as a raw vector
> mode that a function overrides to BLKmode if that particular vector mode is
> not supported. This hunk breaks that assumption and leaks unsupported
> vector modes in the IL of the functions which then have no way to handle
> that, but even before that happens usually it breaks because we try to
> convert_mode between BLKmode and the unsupported vector mode or vice versa
> on PHI nodes.
>
> Alex, do you remember why this has been done?
>
> Patch has been bootstrapped/regtested on x86_64-linux and i686-linux (the
> latter didn't have SSE enabled by default), Jeff said he'll test it on many
> crosses. Ok for trunk if that testing succeeds?
>
> 2019-07-03 Jakub Jelinek <jakub@redhat.com>
>
> PR rtl-optimization/90756
> * explow.c (promote_ssa_mode): Always use TYPE_MODE, don't bypass it
> for VECTOR_TYPE_P.
>
> * gcc.dg/pr90756.c: New test.
Nothing tripped related to this patch in the various targets in my tester.
jeff
prev parent reply other threads:[~2019-07-03 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 7:59 Jakub Jelinek
2019-07-03 8:02 ` Richard Biener
2019-07-03 23:12 ` Jeff Law [this message]
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=9ca8f69a-41b6-804f-6955-6e4046160c6b@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=oliva@adacore.com \
--cc=rguenther@suse.de \
/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).