public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kloczko.tomasz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/107078] New: LTO is causing that firebird build is core dumping
Date: Wed, 28 Sep 2022 21:51:16 +0000 [thread overview]
Message-ID: <bug-107078-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107078
Bug ID: 107078
Summary: LTO is causing that firebird build is core dumping
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: kloczko.tomasz at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
firebird 4.0.2 and gcc-c++ 12.2.1-2 from fedora rawhide.
Build is crashing with sigsegv on execution of the linked binary
Quote from firebird maintainer comment:
"That's almost for sure (99%) pure virtual function call. Usual bug for
dtor/ctor - but I doubt half-constructed node was passed into node
copier. I try to lower compiler optimization level first of all in such
cases (taking into an account that this stuff builds and works OK for
some years)."
More details is in https://github.com/FirebirdSQL/firebird/issues/7308
I found that fedora spec file has disabled LTO as well with comment
# firebird is mis-compiled when LTO is enabled. A root
# cause analysis has not yet been completed. Reported upstream.
# Disable LTO for now
next reply other threads:[~2022-09-28 21:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 21:51 kloczko.tomasz at gmail dot com [this message]
2022-09-28 22:06 ` [Bug lto/107078] " pinskia at gcc dot gnu.org
2022-09-28 22:08 ` pinskia at gcc dot gnu.org
2022-09-29 8:20 ` rguenth at gcc dot gnu.org
2022-09-29 10:20 ` marxin at gcc dot gnu.org
2022-09-29 10:52 ` kloczko.tomasz at gmail dot com
2022-09-29 11:00 ` pinskia at gcc dot gnu.org
2022-09-29 11:01 ` jakub at gcc dot gnu.org
2022-09-29 11:04 ` kloczko.tomasz at gmail dot com
2022-09-29 11:09 ` kloczko.tomasz at gmail dot com
2022-09-29 11:21 ` kloczko.tomasz at gmail dot com
2022-09-29 11:24 ` kloczko.tomasz at gmail dot com
2022-11-01 15:00 ` kloczko.tomasz at gmail dot com
2022-11-10 14:17 ` marxin at gcc dot gnu.org
2022-12-02 13:38 ` marxin at gcc dot gnu.org
2022-12-02 16:53 ` kloczko.tomasz at gmail dot com
2022-12-02 18:27 ` marxin at gcc dot gnu.org
2022-12-02 18:53 ` kloczko.tomasz at gmail dot com
2022-12-02 19:04 ` marxin at gcc dot gnu.org
2022-12-03 10:08 ` sam at gentoo dot org
2022-12-05 9:56 ` marxin at gcc dot gnu.org
2022-12-05 12:23 ` kloczko.tomasz at gmail dot com
2022-12-05 12:27 ` sam at gentoo dot org
2022-12-05 12:32 ` marxin 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-107078-4@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).