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/114034] Failure of tests gcov-dump-{1,2}.C
Date: Tue, 02 Apr 2024 11:30:42 +0000 [thread overview]
Message-ID: <bug-114034-4-cANYjNWgtS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114034-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114034
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:
https://gcc.gnu.org/g:799a056cf804f433ce0050a5a6bf900f7a01ecb1
commit r14-9748-g799a056cf804f433ce0050a5a6bf900f7a01ecb1
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Sun Mar 31 11:22:58 2024 +0100
testsuite: Remove duplicate -lgcov [PR114034]
Duplicate library entries now cause linker warnings with newer linker
versions on Darwin which leads to these tests regressing. The library
is already added by the test flags so there is no need to put an extra
one in the options.
PR testsuite/114034
gcc/testsuite/ChangeLog:
* g++.dg/gcov/gcov-dump-1.C: Remove extra -lgcov.
* g++.dg/gcov/gcov-dump-2.C: Likewise.
Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
next prev parent reply other threads:[~2024-04-02 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 15:28 [Bug target/114034] New: " fxcoudert at gcc dot gnu.org
2024-02-21 15:29 ` [Bug target/114034] " fxcoudert at gcc dot gnu.org
2024-02-21 15:32 ` iains at gcc dot gnu.org
2024-02-21 16:31 ` [Bug testsuite/114034] " pinskia at gcc dot gnu.org
2024-04-02 11:30 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-02 12:25 ` iains at gcc dot gnu.org
2024-04-05 19:58 ` cvs-commit at gcc dot gnu.org
2024-04-22 18:51 ` cvs-commit at gcc dot gnu.org
2024-04-29 14:19 ` cvs-commit at gcc dot gnu.org
2024-04-29 14:43 ` iains 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-114034-4-cANYjNWgtS@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).