public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/99448] ICE in read_cgraph_and_symbols, at lto/lto-common.c:2739
Date: Mon, 08 Mar 2021 09:53:42 +0000 [thread overview]
Message-ID: <bug-99448-4-nbktik1l5f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99448-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99448
--- Comment #2 from Matthias Klose <doko at debian dot org> ---
the compiler is configured with --enable-default-pie.
so this one sometimes fails with different reasons when retrying:
lto1: error: filter/andfiltertest.o: file too short
lto1: fatal error: errors during merging of translation units
compilation terminated.
lto-wrapper: fatal error: g++ returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
and doesn't fail now when just retrying the link command manually now ...
these flags are passed to the upstream build system:
CFLAGS=-g -O2 -ffile-prefix-map=/packages/tmp/log4cxx-0.11.0=. -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2
CXXFLAGS=-g -O2 -ffile-prefix-map=/packages/tmp/log4cxx-0.11.0=. -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
LDFLAGS=-flto=auto -Wl,-z,relro
prev parent reply other threads:[~2021-03-08 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 10:49 [Bug lto/99448] New: " doko at debian dot org
2021-03-08 8:41 ` [Bug lto/99448] " marxin at gcc dot gnu.org
2021-03-08 9:53 ` doko at debian dot org [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-99448-4-nbktik1l5f@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).