https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #19 from Sascha Scandella ---
(In reply to Jonathan Wakely from comment #17)
> The fix has been backported to gcc-13 now. There should be a release
> candidate for 13.2 in the next day or so, please try it out on macOS to make
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #15 from Sascha Scandella ---
For Darwin and GCC 13.1 I've openend a PR with the band-aid fix as proposed by
Jonathan.
https://github.com/Homebrew/homebrew-core/pull/135530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #13 from Sascha Scandella ---
Awesome. Thanks a lot for the provided solution! Nice!
Is already known when approximately GCC 13.2 will be released?
Have a great weekend!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #8 from Sascha Scandella ---
I've tested the proposed solution ...
#if !__has_attribute(__init_priority__) || defined __APPLE__
... and it works as expected. I had also done something similar before, so I
wasn't that surprised.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #6 from Sascha Scandella ---
(In reply to Iain Sandoe from comment #5)
> For now, IMO, we should adopt a fix of the nature Jonathan suggests and then
> it will "just work" if/when we get init prio on Darwin.
Agreed. Sounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #4 from Sascha Scandella ---
I found also this issue regarding init_priority:
https://github.com/llvm/llvm-project/issues/15363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #2 from Sascha Scandella ---
> Still libstdc++ ;-)
True that ;-)
> 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
Bug ID: 110432
Summary: macOS: Segmentation fault when using stdlibc++ from
gcc 13.1 in combination with clang-16
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
