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 rtl-optimization/113617] [14 Regression] Symbol ... referenced in section `.data.rel.ro.local' of ...: defined in discarded section ... since r14-4944 Date: Fri, 08 Mar 2024 14:19:59 +0000 [thread overview] Message-ID: <bug-113617-4-F8crsowT8q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113617-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113617 --- Comment #27 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:8263a4b6505f84973c2ed2fb8d4f2036ca335ff3 commit r14-9392-g8263a4b6505f84973c2ed2fb8d4f2036ca335ff3 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Mar 8 15:18:56 2024 +0100 testsuite: Fix up pr113617 test for darwin [PR113617] The test attempts to link a shared library, and apparently Darwin doesn't allow by default for shared libraries to contain undefined symbols. The following patch just adds dummy definitions for the symbols, so that the library no longer has any undefined symbols at least in my linux testing. Furthermore, for target { !shared } targets (like darwin until the it is fixed in target-supports.exp), because we then link a program rather than shared library, the patch also adds a dummy main definition so that it can link. 2024-03-08 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/113617 PR target/114233 * g++.dg/other/pr113617.C: Define -DSHARED when linking with -shared. * g++.dg/other/pr113617-aux.cc: Add definitions for used methods and templates not defined elsewhere.
prev parent reply other threads:[~2024-03-08 14:20 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-26 13:08 [Bug rtl-optimization/113617] New: " jakub at gcc dot gnu.org 2024-01-26 13:08 ` [Bug rtl-optimization/113617] " jakub at gcc dot gnu.org 2024-01-26 13:09 ` jakub at gcc dot gnu.org 2024-01-26 13:09 ` jakub at gcc dot gnu.org 2024-01-26 13:10 ` jakub at gcc dot gnu.org 2024-01-26 14:22 ` hjl.tools at gmail dot com 2024-01-26 14:28 ` jakub at gcc dot gnu.org 2024-01-26 14:39 ` hjl.tools at gmail dot com 2024-01-26 15:52 ` jakub at gcc dot gnu.org 2024-01-26 15:52 ` jakub at gcc dot gnu.org 2024-01-26 15:52 ` jakub at gcc dot gnu.org 2024-01-26 15:55 ` sjames at gcc dot gnu.org 2024-01-26 16:13 ` jakub at gcc dot gnu.org 2024-01-26 20:44 ` hjl.tools at gmail dot com 2024-01-27 5:53 ` hjl.tools at gmail dot com 2024-01-27 15:13 ` hjl.tools at gmail dot com 2024-01-30 12:45 ` jakub at gcc dot gnu.org 2024-02-14 3:20 ` orion at nwra dot com 2024-02-14 8:20 ` jakub at gcc dot gnu.org 2024-02-26 17:06 ` cvs-commit at gcc dot gnu.org 2024-02-26 17:25 ` jakub at gcc dot gnu.org 2024-03-07 13:31 ` fxcoudert at gcc dot gnu.org 2024-03-07 14:03 ` jakub at gcc dot gnu.org 2024-03-07 14:07 ` fxcoudert at gcc dot gnu.org 2024-03-07 14:08 ` jakub at gcc dot gnu.org 2024-03-07 14:11 ` fxcoudert at gcc dot gnu.org 2024-03-07 14:13 ` jakub at gcc dot gnu.org 2024-03-07 14:20 ` fxcoudert at gcc dot gnu.org 2024-03-07 14:23 ` fxcoudert at gcc dot gnu.org 2024-03-08 14:19 ` cvs-commit at gcc dot gnu.org [this message]
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-113617-4-F8crsowT8q@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).