From: Uros Bizjak <ubizjak@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, x86, testsuite] Two tests that need to be native TLS?
Date: Thu, 30 May 2019 08:51:00 -0000 [thread overview]
Message-ID: <CAFULd4bHHor_Vz9f8jx5swLoRv5fmY+PnD06MFx+FBRSPq_uTw@mail.gmail.com> (raw)
In-Reply-To: <3E4CAD78-B9ED-422B-AED0-2D880C4D30D3@sandoe.co.uk>
On Fri, May 24, 2019 at 9:43 AM Iain Sandoe <iain@sandoe.co.uk> wrote:
>
> Hi Uros,
>
> The following two tests fail on Darwin, which is an emulated TLS target.
> ISTM that the tests really required native support, so that the right fix
> is to require that. (I can skip them for Darwin, if this isn’t the right solution).
The test looks at the output of tls_global_dynamic_64_<mode> pattern,
which is only used with native tls.
> OK?
OK.
Thanks,
Uros.
>
> thanks
> Iain
>
> gcc/testsuite/
>
> * gcc.target/i386/pr86257.c: Require native TLS support.
> * gcc.target/i386/stack-prot-sym.c: Likewise.
>
> diff --git a/gcc/testsuite/gcc.target/i386/pr86257.c b/gcc/testsuite/gcc.target/i386/pr86257.c
> index 07fbba9..bc758c2 100644
> --- a/gcc/testsuite/gcc.target/i386/pr86257.c
> +++ b/gcc/testsuite/gcc.target/i386/pr86257.c
> @@ -1,6 +1,6 @@
> /* { dg-require-effective-target lp64 } */
> /* { dg-require-effective-target fpic } */
> -/* { dg-require-effective-target tls } */
> +/* { dg-require-effective-target tls_native } */
> /* { dg-options "-g -fPIC -mtls-dialect=gnu" } */
>
> __thread int i;
> diff --git a/gcc/testsuite/gcc.target/i386/stack-prot-sym.c b/gcc/testsuite/gcc.target/i386/stack-prot-sym.c
> index 7f63424..dcd7cbd 100644
> --- a/gcc/testsuite/gcc.target/i386/stack-prot-sym.c
> +++ b/gcc/testsuite/gcc.target/i386/stack-prot-sym.c
> @@ -1,4 +1,5 @@
> /* { dg-do compile } */
> +/* { dg-require-effective-target tls_native } */
> /* { dg-options "-O2 -fstack-protector-all -mstack-protector-guard=tls -mstack-protector-guard-reg=gs -mstack-protector-guard-symbol=my_guard" } */
>
> void f(void) { }
>
prev parent reply other threads:[~2019-05-30 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 7:43 Iain Sandoe
2019-05-30 8:51 ` Uros Bizjak [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=CAFULd4bHHor_Vz9f8jx5swLoRv5fmY+PnD06MFx+FBRSPq_uTw@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).