public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114790] ICE when building intel-compute-runtime (error: direct call to ... speculative call sequence has no speculative flag) Date: Mon, 22 Apr 2024 03:48:25 +0000 [thread overview] Message-ID: <bug-114790-4-Jkdt6jX1p0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114790-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114790 --- Comment #7 from Sam James <sjames at gcc dot gnu.org> --- `g++-14 -fPIC -O2 -flto -flto-partition=1to1 -shared -Wl,--version-script=ze.exports reduced-a.ii reduced-b.ii` it violates ODR though: ``` /usr/lib/gcc/x86_64-pc-linux-gnu/14/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/ccvUhonb.o (symbol from plugin): in function `std::aa': (.text+0x0): multiple definition of `L0::pGlobalAPITracerContextImp'; /tmp/cci2r56P.o (symbol from plugin):(.text+0x0): first defined here ```
next prev parent reply other threads:[~2024-04-22 3:48 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-21 1:28 [Bug lto/114790] New: " sjames at gcc dot gnu.org 2024-04-21 1:29 ` [Bug lto/114790] " sjames at gcc dot gnu.org 2024-04-21 1:30 ` sjames at gcc dot gnu.org 2024-04-21 1:30 ` sjames at gcc dot gnu.org 2024-04-21 2:16 ` [Bug ipa/114790] " sjames at gcc dot gnu.org 2024-04-22 3:45 ` sjames at gcc dot gnu.org 2024-04-22 3:46 ` sjames at gcc dot gnu.org 2024-04-22 3:48 ` sjames at gcc dot gnu.org [this message] 2024-04-22 4:10 ` pinskia at gcc dot gnu.org 2024-04-22 4:11 ` pinskia at gcc dot gnu.org 2024-04-22 4:12 ` pinskia at gcc dot gnu.org 2024-04-22 4:14 ` [Bug ipa/114790] [11/12/13/14 regression] " sjames at gcc dot gnu.org 2024-04-22 7:18 ` jakub at gcc dot gnu.org 2024-04-23 13:59 ` sjames at gcc dot gnu.org 2024-04-23 13:59 ` sjames 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-114790-4-Jkdt6jX1p0@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).