public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-308] RISC-V: Add required tls to read thread pointer test
Date: Thu, 27 Apr 2023 15:30:12 +0000 (GMT)	[thread overview]
Message-ID: <20230427153012.B61A33858D33@sourceware.org> (raw)

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

commit r14-308-ge0cf929d99bebd9a740db6db45d69957514e0c12
Author: Pan Li <pan2.li@intel.com>
Date:   Thu Apr 27 11:31:42 2023 +0800

    RISC-V: Add required tls to read thread pointer test
    
    The read-thread-pointer test may require the gcc configured
    with --enable-tls. If no, there x4 (aka tp) register will not
    be presented in the assembly code.
    
    This patch requires the tls for the dg checking. It will perform
    the test checking if --enable-tls and mark the test as unsupported
    if --disable-tls.
    
    Configured with --enable-tls:
    === gcc Summary ===
    of expected passes            16
    
    Configured with --disable-tls:
    === gcc Summary ===
    of unsupported tests          8
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/riscv/read-thread-pointer.c: Add required tls.
    
    Signed-off-by: Pan Li <pan2.li@intel.com>

Diff:
---
 gcc/testsuite/gcc.target/riscv/read-thread-pointer.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.target/riscv/read-thread-pointer.c b/gcc/testsuite/gcc.target/riscv/read-thread-pointer.c
index 401fb421129..5f460b5f746 100644
--- a/gcc/testsuite/gcc.target/riscv/read-thread-pointer.c
+++ b/gcc/testsuite/gcc.target/riscv/read-thread-pointer.c
@@ -1,4 +1,5 @@
 /* { dg-do compile } */
+/* { dg-require-effective-target tls_native } */
 
 void *get_tp()
 {

                 reply	other threads:[~2023-04-27 15:30 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=20230427153012.B61A33858D33@sourceware.org \
    --to=kito@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).