public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113855] New: [14 Regression] __gcc_nested_func_ptr_{created,deleted} exports from 32-bit libgcc_s.so.1 Date: Fri, 09 Feb 2024 23:02:38 +0000 [thread overview] Message-ID: <bug-113855-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113855 Bug ID: 113855 Summary: [14 Regression] __gcc_nested_func_ptr_{created,deleted} exports from 32-bit libgcc_s.so.1 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- Seems when I build i686-linux trunk gcc, __gcc_nested_func_ptr_{created,deleted}@@GCC_14.0.0 is not exported from libgcc_s.so.1, while when I build x86_64-linux trunk gcc, __gcc_nested_func_ptr_{created,deleted}@@GCC_14.0.0 is exported from both 64-bit and 32-bit libgcc. That looks wrong. I guess given the trampoline_insns content it can't really work on ia32, wonder if the whole file shouldn't be wrapped with #ifndef __x86_64__ or similar for now.
next reply other threads:[~2024-02-09 23:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-09 23:02 jakub at gcc dot gnu.org [this message] 2024-02-09 23:03 ` [Bug target/113855] " jakub at gcc dot gnu.org 2024-02-09 23:13 ` iains at gcc dot gnu.org 2024-02-09 23:21 ` jakub at gcc dot gnu.org 2024-02-09 23:22 ` iains at gcc dot gnu.org 2024-02-10 14:03 ` iains at gcc dot gnu.org 2024-02-10 14:12 ` jakub at gcc dot gnu.org 2024-02-12 15:04 ` cvs-commit at gcc dot gnu.org 2024-02-13 10:00 ` jakub at gcc dot gnu.org 2024-02-14 19:56 ` cvs-commit at gcc dot gnu.org 2024-02-14 19:57 ` hjl.tools at gmail dot com
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-113855-4@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).