From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [stage1][PATCH] Lower VEC_COND_EXPR into internal functions.
Date: Wed, 10 Jun 2020 10:51:21 +0200 [thread overview]
Message-ID: <eca3fff1-fc94-8400-9eae-59393a79e968@suse.cz> (raw)
In-Reply-To: <CAFiYyc1v7wc-ZqWRpHcL0xVzdFNXw6kQFA_Ji9uGreEUHdkBgQ@mail.gmail.com>
On 6/9/20 3:42 PM, Richard Biener wrote:
> On Mon, Jun 8, 2020 at 1:04 PM Martin Liška <mliska@suse.cz> wrote:
>>
>> Hello.
>>
>> Thank you for the approval. There's the patch that defines 4 new DEF_INTERNAL_OPTAB_FN.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>> It also builds on ppc64le-linux-gnu.
>>
>> Ready to be installed?
>
> The ChangeLog refers to DEF_INTERNAL_OPTAB_CAN_FAIL which is no longer there.
Sure.
>
> Can you put the isel pass to a separate file please?
Yes.
>
> So this is a first step towards sanitizing VEC_COND_EXPR. There were followups
> mentioned, namely a) enforcing that VEC_COND_EXPR constraint everywhere,
> b) isel vector comparisons at the same time since expansion has a
> vec_cond fallback
I'm planning to work on the follow up.
>
> There's
>
> + /* ??? If we do not cleanup EH then we will ICE in
> + verification. But in reality we have created wrong-code
> + as we did not properly transition EH info and edges to
> + the piecewise computations. */
> + if (maybe_clean_eh_stmt (gsi_stmt (gsi))
> + && gimple_purge_dead_eh_edges (bb))
> + cfg_changed = true;
Hm, I've tried to comment the code in both ISEL and expansion and I can't find a test-case
that would trigger a verification error (in vect.exp and i386.exp). Can you come up with
something that will trigger the code?
>
> which of course is bad. It's the comparison that can throw and I guess current
> RTL expansion manages to cope by find_many_sub_bbs and friends. But we
> need to get this correct on GIMPLE here. Note I find it odd this only triggers
> during ISEL - it should trigger during the lowering step which splits
> the comparison
> from the VEC_COND_EXPR. An appropriate fix at lowering time would be to
> insert the VEC_COND_EXPR w/o the condition on the normal outgoing edge
> and keep the comparison in place of the original VEC_COND_EXPR,
> moving EH info from the VEC_COND_EXPR to the comparison.
Ah ok, so it's about correction of EH..
Martin
>
> I think we need to fix that before merging.
>
> Thanks,
> Richard.
>
>> Thanks,
>> Martin
next prev parent reply other threads:[~2020-06-10 8:51 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 10:25 [PATCH][RFC] Come up with VEC_COND_OP_EXPRs Martin Liška
2019-09-24 11:11 ` Richard Sandiford
2019-09-24 11:29 ` Richard Biener
2019-09-24 11:57 ` Richard Sandiford
2019-09-24 12:18 ` Richard Biener
2019-09-24 14:51 ` Richard Sandiford
2020-04-01 10:19 ` [stage1][PATCH] Lower VEC_COND_EXPR into internal functions Martin Liška
2020-04-06 9:17 ` Richard Sandiford
2020-04-06 12:30 ` Richard Biener
2020-05-21 12:51 ` Martin Liška
2020-05-21 13:29 ` Martin Liška
2020-05-21 20:16 ` Segher Boessenkool
2020-05-22 11:14 ` Richard Biener
2020-05-26 10:15 ` Richard Sandiford
2020-05-27 14:04 ` Martin Liška
2020-05-27 16:13 ` Richard Sandiford
2020-05-27 16:32 ` Richard Biener
2020-05-28 14:46 ` Martin Liška
2020-05-28 15:28 ` Richard Sandiford
2020-05-29 12:17 ` Richard Biener
2020-05-29 12:43 ` Richard Biener
2020-05-29 16:47 ` Segher Boessenkool
2020-05-29 17:05 ` Richard Sandiford
2020-05-29 17:30 ` Segher Boessenkool
2020-05-29 15:39 ` Segher Boessenkool
2020-05-29 16:57 ` Richard Sandiford
2020-05-29 17:09 ` Segher Boessenkool
2020-05-29 17:26 ` Richard Sandiford
2020-05-29 17:37 ` Segher Boessenkool
2020-05-30 7:15 ` Richard Sandiford
2020-05-30 13:08 ` Segher Boessenkool
2020-06-02 11:09 ` Richard Biener
2020-06-02 15:00 ` Martin Liška
2020-06-03 7:38 ` Richard Biener
2020-06-03 13:41 ` Richard Sandiford
2020-06-03 14:17 ` David Edelsohn
2020-06-03 14:46 ` Richard Biener
2020-06-03 17:01 ` Segher Boessenkool
2020-06-03 17:23 ` Richard Biener
2020-06-03 18:23 ` Segher Boessenkool
2020-06-03 18:38 ` Richard Biener
2020-06-03 18:46 ` David Edelsohn
2020-06-03 19:09 ` Segher Boessenkool
2020-06-03 19:13 ` Jakub Jelinek
2020-06-03 18:27 ` Segher Boessenkool
2020-06-08 11:04 ` Martin Liška
2020-06-09 13:42 ` Richard Biener
2020-06-10 8:51 ` Martin Liška [this message]
2020-06-10 10:50 ` Richard Biener
2020-06-10 12:27 ` Martin Liška
2020-06-10 13:01 ` Martin Liška
2020-06-11 8:52 ` Martin Liška
2020-06-12 9:43 ` Richard Biener
2020-06-12 13:24 ` Martin Liška
2020-06-15 7:14 ` Richard Biener
2020-06-15 11:19 ` Martin Liška
2020-06-15 11:59 ` Richard Biener
2020-06-15 12:20 ` Martin Liška
2020-06-17 8:50 ` Richard Biener
2020-06-17 13:15 ` Richard Biener
2020-06-18 8:10 ` Martin Liška
2020-06-18 8:52 ` Richard Biener
2020-06-18 9:02 ` Martin Liška
2020-06-18 9:29 ` Martin Liška
2020-04-06 12:33 ` Richard Biener
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=eca3fff1-fc94-8400-9eae-59393a79e968@suse.cz \
--to=mliska@suse.cz \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.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).