public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/114614] New test case gcc.misc-tests/gcov-20.c from r14-9789-g08a52331803f66 fails
Date: Tue, 09 Apr 2024 02:03:57 +0000	[thread overview]
Message-ID: <bug-114614-4-GWXSPtT2oY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114614-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114614

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

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.

  parent reply	other threads:[~2024-04-09  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 21:17 [Bug testsuite/114614] New: " seurer at gcc dot gnu.org
2024-04-08  1:10 ` [Bug testsuite/114614] " linkw at gcc dot gnu.org
2024-04-09  2:03 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-09  2:09 ` linkw at gcc dot gnu.org

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=bug-114614-4-GWXSPtT2oY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).