public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Thu, 14 May 2020 13:20:38 +0000 [thread overview]
Message-ID: <bug-92658-4-TKEODtAE6q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 14 May 2020, ubizjak at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
>
> --- Comment #10 from Uroš Bizjak <ubizjak at gmail dot com> ---
> The patch is ready to be pushed, it is waiting for a decision what to do with
> failed cases.
>
> Richi, should this patch move forward (eventually XFAILing failed cases), or do
> you plan to look at the fails from the generic vectorizer POV?
I think we should go forward with the patch, either XFAILing the testcases
or splitting out the testcase (and backend patterns that do not get
exercised due to the issue).
I've already said in comment#8 that the issue here is optabs working
with modes and not vector types, so it's a bit hard to use the
same mechanism to deal with the currently failing cases. One
possible route would be to add V4QImode similar to how we now
do V2SFmode with SSE but of course where do we stop ...
As said we can try to tackle this incrementally. Maybe Richard also
has input here?
next prev parent reply other threads:[~2020-05-14 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92658-4@http.gcc.gnu.org/bugzilla/>
2020-05-14 12:50 ` ubizjak at gmail dot com
2020-05-14 13:20 ` rguenther at suse dot de [this message]
2020-05-14 13:41 ` rsandifo at gcc dot gnu.org
2020-05-15 8:18 ` crazylht at gmail dot com
2020-05-19 9:26 ` cvs-commit at gcc dot gnu.org
2020-05-19 9:35 ` ubizjak at gmail dot com
2020-05-20 5:12 ` crazylht at gmail dot com
2020-05-20 8:16 ` crazylht at gmail dot com
2020-05-22 13:32 ` cvs-commit at gcc dot gnu.org
2020-05-22 21:50 ` mark at gcc dot gnu.org
2020-05-23 2:28 ` crazylht at gmail dot com
2020-12-25 2:19 ` crazylht at gmail dot com
2020-12-25 10:32 ` ubizjak at gmail dot com
2020-12-29 1:36 ` crazylht at gmail dot com
2021-01-07 6:35 ` cvs-commit at gcc dot gnu.org
2021-12-15 0:53 ` pinskia at gcc dot gnu.org
2021-12-15 1:46 ` crazylht at gmail dot com
2023-05-10 20:43 ` cvs-commit at gcc dot gnu.org
2023-06-03 0:09 ` cvs-commit 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-92658-4-TKEODtAE6q@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).