public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114189] New: Target implements obsolete vcond{,u,eq} expanders
Date: Fri, 01 Mar 2024 10:16:05 +0000 [thread overview]
Message-ID: <bug-114189-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114189
Bug ID: 114189
Summary: Target implements obsolete vcond{,u,eq} expanders
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
The listed targets implement any of vcond, vcondu or vcondeq expanders where
the modern way of exposing vector conditional instructions is using
mask generating vec_cmp{,u,eq} and vcond_mask expanders.
vcond, vcondu and vcondeq optabs will be retired in the future.
next reply other threads:[~2024-03-01 10:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 10:16 rguenth at gcc dot gnu.org [this message]
2024-03-01 10:23 ` [Bug target/114189] " rguenth at gcc dot gnu.org
2024-06-14 10:24 ` rguenth at gcc dot gnu.org
2024-06-17 5:47 ` rguenth at gcc dot gnu.org
2024-06-17 5:48 ` rguenth at gcc dot gnu.org
2024-06-17 15:48 ` pinskia at gcc dot gnu.org
2024-06-26 3:13 ` cvs-commit at gcc dot gnu.org
2024-07-01 5:27 ` liuhongt at gcc dot gnu.org
2024-07-12 6:44 ` linkw at gcc dot gnu.org
2024-07-12 7:11 ` rguenth at gcc dot gnu.org
2024-07-12 8:51 ` ebotcazou at gcc dot gnu.org
2024-07-12 12:45 ` rguenther at suse dot de
2024-07-16 8:43 ` cvs-commit at gcc dot gnu.org
2024-07-22 18:17 ` pinskia at gcc dot gnu.org
2024-07-22 21:06 ` pinskia at gcc dot gnu.org
2024-08-02 9:36 ` rguenth at gcc dot gnu.org
2024-08-02 9:41 ` rguenth at gcc dot gnu.org
2024-08-08 17:59 ` pinskia at gcc dot gnu.org
2024-08-12 1:33 ` cvs-commit at gcc dot gnu.org
2024-08-19 13:05 ` rguenth 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-114189-4@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).