public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/113402] Incorrect symbol versions for __builtin_nested_func_ptr_created, __builtin_nested_func_ptr in libgcc_s.so.1 Date: Mon, 15 Jan 2024 16:44:04 +0000 [thread overview] Message-ID: <bug-113402-4-RRAocKLlhk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113402-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113402 --- Comment #1 from Florian Weimer <fw at gcc dot gnu.org> --- I should say I have only tested this on x86-64, but it is likely that this impacts other supported ABIs as well.
next prev parent reply other threads:[~2024-01-15 16:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 16:38 [Bug libgcc/113402] New: Incorrect symbol versions for __builtin_nested_func_ptr_created, __builtin_nested_func_ptr fw at gcc dot gnu.org 2024-01-15 16:44 ` fw at gcc dot gnu.org [this message] 2024-01-15 17:00 ` [Bug libgcc/113402] Incorrect symbol versions for __builtin_nested_func_ptr_created, __builtin_nested_func_ptr in libgcc_s.so.1 jakub at gcc dot gnu.org 2024-01-15 20:30 ` iains at gcc dot gnu.org 2024-01-16 8:00 ` rguenth at gcc dot gnu.org 2024-01-28 11:00 ` cvs-commit at gcc dot gnu.org 2024-01-31 18:33 ` danglin at gcc dot gnu.org 2024-01-31 18:35 ` jakub at gcc dot gnu.org 2024-02-01 20:10 ` cvs-commit at gcc dot gnu.org 2024-03-17 2:47 ` iains at gcc dot gnu.org 2024-03-17 15:43 ` dave.anglin at bell dot net 2024-03-27 15:49 ` egallager 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-113402-4-RRAocKLlhk@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).