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++/110432] macOS: Segmentation fault when using stdlibc++ from gcc 13.1 in combination with clang-16 Date: Tue, 27 Jun 2023 10:27:20 +0000 [thread overview] Message-ID: <bug-110432-4-e6P2eUkcrE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110432-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-06-27 Status|UNCONFIRMED |NEW Keywords| |ABI CC| |ppalka at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Sascha Scandella from comment #0) > This leads to a segmentation fault with a simple sample application when > using clang-16 in combination with stdlibc++. It's libstdc++ > Would it be possible to change the #if statement such that it would also > work on macOS when using clang in combination with the stdlibc++? Still libstdc++ ;-) > #if !__has_attribute(__init_priority__) > static ios_base::Init __ioinit; > #elif defined(_GLIBCXX_SYMVER_GNU) > __extension__ __asm (".globl _ZSt21ios_base_library_initv"); > #endif Patrick, we talked about this and IIRC your suggestion was to move the __has_attribute check into configure, so that it depends on GCC, not on whichever compiler happens to include <iostream> later.
next prev parent reply other threads:[~2023-06-27 10:27 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-27 9:56 [Bug libstdc++/110432] New: " sascha.scandella at dentsplysirona dot com 2023-06-27 10:27 ` redi at gcc dot gnu.org [this message] 2023-06-27 10:32 ` [Bug libstdc++/110432] " sascha.scandella at dentsplysirona dot com 2023-06-27 10:46 ` iains at gcc dot gnu.org 2023-06-27 10:50 ` sascha.scandella at dentsplysirona dot com 2023-06-27 11:05 ` iains at gcc dot gnu.org 2023-06-27 12:08 ` sascha.scandella at dentsplysirona dot com 2023-06-27 12:09 ` redi at gcc dot gnu.org 2023-06-29 15:54 ` sascha.scandella at dentsplysirona dot com 2023-06-29 16:09 ` ppalka at gcc dot gnu.org 2023-06-29 16:12 ` iains at gcc dot gnu.org 2023-06-29 16:28 ` redi at gcc dot gnu.org 2023-06-30 14:37 ` cvs-commit at gcc dot gnu.org 2023-06-30 15:19 ` sascha.scandella at dentsplysirona dot com 2023-06-30 15:25 ` jakub at gcc dot gnu.org 2023-07-01 14:11 ` sascha.scandella at dentsplysirona dot com 2023-07-19 19:35 ` cvs-commit at gcc dot gnu.org 2023-07-19 19:36 ` redi at gcc dot gnu.org 2023-07-20 11:58 ` redi at gcc dot gnu.org 2023-08-07 13:04 ` sascha.scandella at dentsplysirona 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-110432-4-e6P2eUkcrE@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).