public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebunger44 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/113183] LTO crashes with Segmentation fault
Date: Sat, 30 Dec 2023 20:25:06 +0000	[thread overview]
Message-ID: <bug-113183-4-vwBjKwyZIw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113183-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113183

--- Comment #13 from Sebastian Unger <sebunger44 at gmail dot com> ---
No worries, the constructor attribute is much better. I was aware of that, but
at the time had already several examples using .preinit_array and couldn't be
bothered to look it up. I later added the sort by priority and added priorities
to  the *init_array symbols that needed them, but not this one. Interestingly,
that was not when LTO started crashing (or I might have made the connection).
LTO only started crashing once I added the static global object NonTrivial!
Weird.

In any case, I have changed to the constructor attribute and learned my lesson
and am all good.

I'll leave this issue open in case someone wants to fix the crash in LD (or
wherever it comes from) so people running into this in the future will get a
nicer error message.

      parent reply	other threads:[~2023-12-30 20:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 19:35 [Bug lto/113183] New: " sebunger44 at gmail dot com
2023-12-30 19:40 ` [Bug lto/113183] " pinskia at gcc dot gnu.org
2023-12-30 19:43 ` pinskia at gcc dot gnu.org
2023-12-30 19:44 ` pinskia at gcc dot gnu.org
2023-12-30 19:45 ` sebunger44 at gmail dot com
2023-12-30 19:46 ` pinskia at gcc dot gnu.org
2023-12-30 19:48 ` pinskia at gcc dot gnu.org
2023-12-30 19:48 ` sebunger44 at gmail dot com
2023-12-30 19:49 ` sebunger44 at gmail dot com
2023-12-30 19:49 ` sebunger44 at gmail dot com
2023-12-30 19:54 ` pinskia at gcc dot gnu.org
2023-12-30 20:00 ` sebunger44 at gmail dot com
2023-12-30 20:20 ` pinskia at gcc dot gnu.org
2023-12-30 20:25 ` sebunger44 at gmail dot com [this message]

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-113183-4-vwBjKwyZIw@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).