From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw <richard.earnshaw@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
richard.sandiford@arm.com
Subject: Re: [PATCH] aarch64: enforce lane checking for intrinsics
Date: Mon, 29 Jan 2024 16:00:19 -0300 [thread overview]
Message-ID: <orjznshsn0.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <mptle8gkz5q.fsf@arm.com> (Richard Sandiford's message of "Tue, 23 Jan 2024 12:33:05 +0000")
On Jan 23, 2024, Richard Sandiford <richard.sandiford@arm.com> wrote:
> Performing the check in expand is itself wrong
*nod*
> So I think we should enforce the immediate range within the frontend
> instead, via TARGET_CHECK_BUILTIN_CALL.
Sounds good. Can that accommodate the existing uses in always_inline
wrappers?
> Unfortunately that isn't suitable for stage 4 though.
ACK. Is there a partial implementation of that? I might get a chance
to take it to completion, even if it doesn't make gcc 14.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
next prev parent reply other threads:[~2024-01-29 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 7:11 Alexandre Oliva
2024-01-23 12:33 ` Richard Sandiford
2024-01-29 19:00 ` Alexandre Oliva [this message]
2024-01-29 21:21 ` Richard Sandiford
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=orjznshsn0.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=marcus.shawcroft@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@arm.com \
/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).