public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1343] libgomp: Compile tests with -march=i486 only if needed
Date: Wed,  9 Jun 2021 17:06:08 +0000 (GMT)	[thread overview]
Message-ID: <20210609170608.B9D1A399C014@sourceware.org> (raw)

https://gcc.gnu.org/g:c8d581bdf731714977b1592e74d05e000535e338

commit r12-1343-gc8d581bdf731714977b1592e74d05e000535e338
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sun Jun 6 05:36:23 2021 -0700

    libgomp: Compile tests with -march=i486 only if needed
    
    Don't add -march=i486 if atomic compare-and-swap is supported on 'int'.
    This fixes libgomp tests with "-march=x86-64 -m32 -fcf-protection".
    
            * testsuite/lib/libgomp.exp (libgomp_init): Don't add -march=i486
            if atomic compare-and-swap is supported on 'int'.

Diff:
---
 libgomp/testsuite/lib/libgomp.exp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libgomp/testsuite/lib/libgomp.exp b/libgomp/testsuite/lib/libgomp.exp
index 45c78d8510e..a2050151e84 100644
--- a/libgomp/testsuite/lib/libgomp.exp
+++ b/libgomp/testsuite/lib/libgomp.exp
@@ -210,7 +210,8 @@ proc libgomp_init { args } {
 
     # We use atomic operations in the testcases to validate results.
     if { ([istarget i?86-*-*] || [istarget x86_64-*-*])
-	 && [check_effective_target_ia32] } {
+	 && [check_effective_target_ia32]
+	 && ![check_effective_target_cas_char] } {
 	lappend ALWAYS_CFLAGS "additional_flags=-march=i486"
     }


                 reply	other threads:[~2021-06-09 17:06 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=20210609170608.B9D1A399C014@sourceware.org \
    --to=hjl@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: 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).