public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5827] testsuite: Fix check_effective_target_rop_ok [PR103556, PR103586] Date: Tue, 7 Dec 2021 20:43:43 +0000 (GMT) [thread overview] Message-ID: <20211207204343.2BC7B3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:4394fd67264f5de650c2c3509c001c5f7203449d commit r12-5827-g4394fd67264f5de650c2c3509c001c5f7203449d Author: Peter Bergner <bergner@linux.ibm.com> Date: Tue Dec 7 14:42:38 2021 -0600 testsuite: Fix check_effective_target_rop_ok [PR103556, PR103586] The new rop_ok effective target test doesn't correctly compute its expression result because a new line starts a new statement. Solution is to remove the new line. 2021-12-07 Peter Bergner <bergner@linux.ibm.com> gcc/testsuite/ PR testsuite/103556 PR testsuite/103586 * lib/target-supports.exp (check_effective_target_rop_ok): Remove '\n'. Diff: --- gcc/testsuite/lib/target-supports.exp | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 7956c387c55..039125c866a 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -6631,8 +6631,7 @@ proc check_effective_target_powerpc_elfv2 { } { # Return 1 if this is a PowerPC target supporting -mrop-protect proc check_effective_target_rop_ok { } { - return [check_effective_target_power10_ok] - && [check_effective_target_powerpc_elfv2] + return [check_effective_target_power10_ok] && [check_effective_target_powerpc_elfv2] } # The VxWorks SPARC simulator accepts only EM_SPARC executables and
reply other threads:[~2021-12-07 20:43 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=20211207204343.2BC7B3858D28@sourceware.org \ --to=bergner@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).