public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Matthew Malcomson <matmal01@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ARM/heads/morello)] Fix caching name on cheri_capability_pure selector Date: Tue, 21 Sep 2021 09:15:36 +0000 (GMT) [thread overview] Message-ID: <20210921091536.A1D1B3858413@sourceware.org> (raw) https://gcc.gnu.org/g:1fc5b16e1792f871bd694969f4b77b25c50970a9 commit 1fc5b16e1792f871bd694969f4b77b25c50970a9 Author: Matthew Malcomson <matthew.malcomson@arm.com> Date: Thu Sep 16 11:34:14 2021 +0100 Fix caching name on cheri_capability_pure selector The check_effective_target_cheri_capability_pure procedure uses check_no_compiler_messages as many others do. This procedure takes a cache variable name to record whether we are supporting this feature. The variable name that cheri_capability_pure used was aarch64_capability_any, which meant that if we'd found that any capability was available we would assume that pure capability was available. This was a particular problem in the morello.exp testsuite since some tests are designed specifically for PureCap while others can be run for Fake Cap too. Here we assign a cache variable specifically for if PureCap is available and use that in the relevant procedure. This fixes the testsuite for the new PureCap only tests recently added. Diff: --- gcc/testsuite/lib/target-supports.exp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index f438de2e323..be4f0e6db73 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -3571,7 +3571,7 @@ proc check_effective_target_cheri_capability_pure { } { if { ![istarget aarch64*-*-*] } { return 0 } - return [check_no_compiler_messages aarch64_capability_any assembly { + return [check_no_compiler_messages cheri_capability_pure assembly { #if !defined (__CHERI_PURE_CAPABILITY__) #error foo #endif
reply other threads:[~2021-09-21 9:15 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210921091536.A1D1B3858413@sourceware.org \ --to=matmal01@gcc.gnu.org \ --cc=gcc-cvs@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).