public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5220] Remove reference to Solaris 9 in comment of add_options_for_tls Date: Mon, 16 Jan 2023 23:58:54 +0000 (GMT) [thread overview] Message-ID: <20230116235854.A60B4385842A@sourceware.org> (raw) https://gcc.gnu.org/g:35627c5fb6a51e31ae651a0c79f0775f4290a86e commit r13-5220-g35627c5fb6a51e31ae651a0c79f0775f4290a86e Author: Andrew Pinski <apinski@marvell.com> Date: Mon Jan 16 23:53:33 2023 +0000 Remove reference to Solaris 9 in comment of add_options_for_tls Since r5-172-gd9f069ab4f6450, the code no longer matches the comment as the code for Solaris 9 support was removed. This just updates the comment to reference AIX only as the code does. Committed as obvious. gcc/testsuite/ChangeLog: * lib/target-supports.exp (add_options_for_tls): Remove reference to Solaris 9 in comments. Diff: --- gcc/testsuite/lib/target-supports.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index b906d4004be..38b95145117 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -869,8 +869,8 @@ proc check_effective_target_pcc_bitfield_type_matters { } { # Add to FLAGS all the target-specific flags needed to use thread-local storage. proc add_options_for_tls { flags } { - # On Solaris 9, __tls_get_addr/___tls_get_addr only lives in - # libthread, so always pass -pthread for native TLS. Same for AIX. + # On AIX, __tls_get_addr/___tls_get_addr only lives in + # libthread, so always pass -pthread for native TLS. # Need to duplicate native TLS check from # check_effective_target_tls_native to avoid recursion. if { ([istarget powerpc-ibm-aix*]) &&
reply other threads:[~2023-01-16 23:58 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=20230116235854.A60B4385842A@sourceware.org \ --to=pinskia@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).