public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains 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 11:05:24 +0000	[thread overview]
Message-ID: <bug-110432-4-t8Y12qEPqK@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

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Sascha Scandella from comment #4)
> I found also this issue regarding init_priority:
> https://github.com/llvm/llvm-project/issues/15363

So that is the intentional behaviour (upstream clang definitely used to reject
it) - as noted it actually works fine with LTO too (or within one module if
not).

I was investigating whether we could do the work in collect2, but that gets
quite complex when considering the interactions between LTO and non-LTO
objects.

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.

in slower time, we might consider the option of following clang's behaviour for
Darwin (possibly with a warning about the does-not-work-between-tus).

  parent reply	other threads:[~2023-06-27 11:05 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 ` [Bug libstdc++/110432] " redi at gcc dot gnu.org
2023-06-27 10:32 ` 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 [this message]
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-t8Y12qEPqK@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: link
Be 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).