From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Add "futex" and "gthreads" effective-target keywords
Date: Thu, 26 Nov 2020 22:56:34 +0000 [thread overview]
Message-ID: <20201126225634.GO1312820@redhat.com> (raw)
In-Reply-To: <20201126171033.GM1312820@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On 26/11/20 17:10 +0000, Jonathan Wakely wrote:
>On 26/11/20 16:25 +0000, Jonathan Wakely wrote:
>>+# Return 1 if futex syscall is available
>>+proc check_effective_target_gthreads { } {
>>+ return [check_v3_target_gthreads_timed]
>
>Oops, I've just noticed the comment is wrong and this calls the wrong
>proc. It should be check_v3_target_gthreads not
>check_v3_target_gthreads_timed.
>
>I'm in the process of refactoring it anyway so will fix it.
The refactoring is gling slowly, so here the fix.
Tested powerpc64le-linux. Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1451 bytes --]
commit 1a00786414c7ee2f228562fab5c43491a13284c1
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Nov 26 21:41:15 2020
libstc++: Fix typo in new check_effective_target_gthreads proc
Also fix copy&pasted comments referring to the wrong things.
libstdc++-v3/ChangeLog:
* testsuite/lib/libstdc++.exp (check_effective_target_gthreads):
Call check_v3_target_gthreads not check_v3_target_gthreads_timed.
diff --git a/libstdc++-v3/testsuite/lib/libstdc++.exp b/libstdc++-v3/testsuite/lib/libstdc++.exp
index bde8cc0cc91f..b94116ff4ea5 100644
--- a/libstdc++-v3/testsuite/lib/libstdc++.exp
+++ b/libstdc++-v3/testsuite/lib/libstdc++.exp
@@ -1619,7 +1619,8 @@ proc check_effective_target_tbb-backend { } {
# Return 1 if futex syscall is available
proc check_effective_target_futex { } {
return [check_v3_target_prop_cached et_futex {
- # Set up and compile a C++ test program that depends on tbb
+ # Set up and compile a C++ test program that depends on futex
+ # being supported.
set src futex[pid].cc
set exe futex[pid].x
@@ -1643,9 +1644,10 @@ proc check_effective_target_futex { } {
}]
}
-# Return 1 if futex syscall is available
+# Return 1 if C++11 [threads] facilities are available via gthreads,
+# 0 otherwise.
proc check_effective_target_gthreads { } {
- return [check_v3_target_gthreads_timed]
+ return [check_v3_target_gthreads]
}
set additional_prunes ""
prev parent reply other threads:[~2020-11-26 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 16:25 Jonathan Wakely
2020-11-26 17:10 ` Jonathan Wakely
2020-11-26 22:56 ` Jonathan Wakely [this message]
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=20201126225634.GO1312820@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).