public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112397] Two persistent libstdc++ test failures on x86_64-apple-darwin Date: Mon, 06 Nov 2023 09:19:42 +0000 [thread overview] Message-ID: <bug-112397-4-h5MNCWCMyp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112397-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iains at gcc dot gnu.org --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- The .cold symbol is created by gcc, I don't see any way to control its visibility in the source. So maybe a target bug in the compiler, not a library bug.
next prev parent reply other threads:[~2023-11-06 9:19 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-05 20:42 [Bug libstdc++/112397] New: " fxcoudert at gcc dot gnu.org 2023-11-06 9:19 ` redi at gcc dot gnu.org [this message] 2023-11-06 16:17 ` [Bug target/112397] " iains at gcc dot gnu.org 2024-02-07 17:37 ` iains at gcc dot gnu.org 2024-02-08 12:11 ` redi at gcc dot gnu.org 2024-02-08 12:15 ` redi at gcc dot gnu.org 2024-02-08 12:21 ` jakub at gcc dot gnu.org 2024-02-08 13:12 ` iains at gcc dot gnu.org 2024-02-08 13:18 ` jakub at gcc dot gnu.org 2024-02-08 13:22 ` jakub at gcc dot gnu.org 2024-02-08 14:02 ` iains at gcc dot gnu.org 2024-02-19 20:16 ` cvs-commit at gcc dot gnu.org 2024-04-03 14:57 ` cvs-commit at gcc dot gnu.org 2024-04-21 13:04 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:18 ` 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-112397-4-h5MNCWCMyp@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).