public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96914] missing MVE intrinsics
Date: Mon, 05 Oct 2020 15:24:07 +0000 [thread overview]
Message-ID: <bug-96914-4-rOAjC00Rxp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96914-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96914
avieira at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |avieira at gcc dot gnu.org
--- Comment #5 from avieira at gcc dot gnu.org ---
Hi Christophe,
The docs are right and so are you, those instructions should only have a signed
variant as the hardware instructions also only supports .S suffixes or in the
case of vmlaldavax do not support the cross 'X' variant with unsigned
datatypes.
next prev parent reply other threads:[~2020-10-05 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:10 [Bug target/96914] New: " clyon at gcc dot gnu.org
2020-09-03 9:10 ` [Bug target/96914] " clyon at gcc dot gnu.org
2020-10-05 12:19 ` clyon at gcc dot gnu.org
2020-10-05 12:33 ` clyon at gcc dot gnu.org
2020-10-05 13:25 ` clyon at gcc dot gnu.org
2020-10-05 14:10 ` clyon at gcc dot gnu.org
2020-10-05 15:24 ` avieira at gcc dot gnu.org [this message]
2020-10-06 8:27 ` clyon at gcc dot gnu.org
2020-10-08 11:12 ` cvs-commit at gcc dot gnu.org
2020-10-08 11:13 ` cvs-commit at gcc dot gnu.org
2020-10-08 14:19 ` cvs-commit at gcc dot gnu.org
2020-10-08 14:20 ` clyon at gcc dot gnu.org
2020-10-16 12:35 ` cvs-commit at gcc dot gnu.org
2020-10-16 12:35 ` cvs-commit at gcc dot gnu.org
2020-10-16 12:35 ` 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-96914-4-rOAjC00Rxp@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).