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 target/114036] Test failure of gcov-14.c on darwin Date: Sun, 21 Apr 2024 13:05:46 +0000 [thread overview] Message-ID: <bug-114036-4-anbspUOX8J@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114036-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:ed046c2cc0f0a2d00cc77e5e9ce5d8f71e2278c6 commit r12-10379-ged046c2cc0f0a2d00cc77e5e9ce5d8f71e2278c6 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Mar 31 11:27:53 2024 +0100 testsuite, Darwin: Allow for an undefined symbol [PR114036]. Darwin's linker defaults to requiring all symbols to be defined at static link time (unless specifically noted or dynamic lookuo is enabled). For this test, we just need to note that the symbol is expected to be undefined. PR testsuite/114036 gcc/testsuite/ChangeLog: * gcc.misc-tests/gcov-14.c: Allow for 'Foo' to be undefined on Darwin link lines. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> (cherry picked from commit ad8e34eaa870608e2b07b4e7147e6ef2944bb8b5)
next prev parent reply other threads:[~2024-04-21 13:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-21 15:35 [Bug target/114036] New: " fxcoudert at gcc dot gnu.org 2024-02-21 15:35 ` [Bug target/114036] " fxcoudert at gcc dot gnu.org 2024-02-21 15:43 ` iains at gcc dot gnu.org 2024-02-21 15:44 ` iains at gcc dot gnu.org 2024-02-21 15:47 ` fxcoudert at gcc dot gnu.org 2024-04-02 11:27 ` cvs-commit at gcc dot gnu.org 2024-04-02 12:24 ` iains at gcc dot gnu.org 2024-04-04 18:36 ` cvs-commit at gcc dot gnu.org 2024-04-21 13:05 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-29 14:19 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:42 ` 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-114036-4-anbspUOX8J@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: linkBe 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).