public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9851] testsuite: Add profile_update_atomic check to gcov-20.c [PR114614]
Date: Tue,  9 Apr 2024 02:03:55 +0000 (GMT)	[thread overview]
Message-ID: <20240409020356.26673385842A@sourceware.org> (raw)

https://gcc.gnu.org/g:9c97de682303b81c8886ac131fcfb3b122f2f1a6

commit r14-9851-g9c97de682303b81c8886ac131fcfb3b122f2f1a6
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon Apr 8 21:02:17 2024 -0500

    testsuite: Add profile_update_atomic check to gcov-20.c [PR114614]
    
    As PR114614 shows, the newly added test case gcov-20.c by
    commit r14-9789-g08a52331803f66 failed on targets which do
    not support atomic profile update, there would be a message
    like:
    
      warning: target does not support atomic profile update,
               single mode is selected
    
    Since the test case adopts -fprofile-update=atomic, it
    requires effective target check profile_update_atomic, this
    patch is to add the check accordingly.
    
            PR testsuite/114614
    
    gcc/testsuite/ChangeLog:
    
            * gcc.misc-tests/gcov-20.c: Add effective target check
            profile_update_atomic.

Diff:
---
 gcc/testsuite/gcc.misc-tests/gcov-20.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.misc-tests/gcov-20.c b/gcc/testsuite/gcc.misc-tests/gcov-20.c
index 215faffc980..ca8c12aad2b 100644
--- a/gcc/testsuite/gcc.misc-tests/gcov-20.c
+++ b/gcc/testsuite/gcc.misc-tests/gcov-20.c
@@ -1,5 +1,6 @@
 /* { dg-options "-fcondition-coverage -ftest-coverage -fprofile-update=atomic" } */
 /* { dg-do run { target native } } */
+/* { dg-require-effective-target profile_update_atomic } */
 
 /* Some side effect to stop branches from being pruned */
 int x = 0;

                 reply	other threads:[~2024-04-09  2:03 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=20240409020356.26673385842A@sourceware.org \
    --to=linkw@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).