public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112108] [aarch64] Some intrinsics are not correctly enabled when using 'target' attributes Date: Wed, 04 Sep 2024 18:27:33 +0000 [thread overview] Message-ID: <bug-112108-4-BAjTAaCpLa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112108-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112108 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Andrew Carlotti <acarlotti@gcc.gnu.org>: https://gcc.gnu.org/g:0a3a0d4a5e32e9b914b5c5cc283ee485adc6cd11 commit r14-10633-g0a3a0d4a5e32e9b914b5c5cc283ee485adc6cd11 Author: Andrew Carlotti <andrew.carlotti@arm.com> Date: Thu Oct 26 15:43:44 2023 +0100 aarch64: Fix tme intrinsic availability The availability of tme intrinsics was previously gated at both initialisation time (using global target options) and usage time (accounting for function-specific target options). This patch removes the check at initialisation time, and also moves the intrinsics out of the header file to allow for better error messages (matching the existing error messages for SVE intrinsics). gcc/ChangeLog: PR target/112108 * config/aarch64/aarch64-builtins.cc (aarch64_init_tme_builtins): Define intrinsic names directly. (aarch64_general_init_builtins): Move tme initialisation... (handle_arm_acle_h): ...to here, and remove feature check. (aarch64_general_check_builtin_call): Check tme intrinsics. * config/aarch64/arm_acle.h (__tstart, __tcommit, __tcancel) (__ttest): Remove. (_TMFAILURE_*): Define unconditionally. gcc/testsuite/ChangeLog: PR target/112108 * gcc.target/aarch64/acle/tme_guard-1.c: New test. * gcc.target/aarch64/acle/tme_guard-2.c: New test. * gcc.target/aarch64/acle/tme_guard-3.c: New test. * gcc.target/aarch64/acle/tme_guard-4.c: New test.
next prev parent reply other threads:[~2024-09-04 18:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-27 14:05 [Bug target/112108] New: " andrew.carlotti at arm dot com 2023-11-04 5:37 ` [Bug target/112108] " pinskia at gcc dot gnu.org 2024-08-19 14:50 ` cvs-commit at gcc dot gnu.org 2024-08-19 14:50 ` cvs-commit at gcc dot gnu.org 2024-08-19 14:50 ` cvs-commit at gcc dot gnu.org 2024-09-04 18:27 ` cvs-commit at gcc dot gnu.org [this message] 2024-09-04 18:27 ` cvs-commit at gcc dot gnu.org 2024-09-04 18:27 ` 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-112108-4-BAjTAaCpLa@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: linkBe 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).