public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug analyzer/99854] New: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer
@ 2021-03-31 18:07 jseward at acm dot org
2021-03-31 18:28 ` [Bug analyzer/99854] " dmalcolm at gcc dot gnu.org
2021-03-31 18:37 ` jseward at acm dot org
0 siblings, 2 replies; 3+ messages in thread
From: jseward at acm dot org @ 2021-03-31 18:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854
Bug ID: 99854
Summary: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph
edge statement index out of range" when building
Valgrind with LTO and -fanalyzer
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: jseward at acm dot org
Target Milestone: ---
Building Valgrind trunk on x86_64-linux with gcc (GCC) 11.0.1 20210328
(experimental) fails with
In function ‘setregs’:
lto1: fatal error: Cgraph edge statement index out of range
This requires both LTO and -fanalyzer to fail. Either by itself does not fail.
STR on x86_64-linux, Fedora 33:
git clone git://sourceware.org/git/valgrind.git
cd valgrind
# apply one-line config patch below, so as to build with -fanalyzer
./autogen.sh && ./configure --prefix=`pwd`/Inst --enable-only64bit
--enable-lto
make -j8
Fails thusly:
In function ‘myvprintf_str_XML_simplistic’:
lto1: fatal error: Cgraph edge statement index out of range
and
In function ‘setregs’:
lto1: fatal error: Cgraph edge statement index out of range
(takes about 25 seconds).
Sorry not to have minimised. Am willing to try out patches.
Config patch as referred to above:
diff --git a/Makefile.all.am b/Makefile.all.am
index bcd29165d..c339b95c7 100644
--- a/Makefile.all.am
+++ b/Makefile.all.am
@@ -96,7 +96,7 @@ clean-noinst_DSYMS:
# performance and get whatever useful warnings we can out of gcc.
# -fno-builtin is important for defeating LLVM's idiom recognition
# that somehow causes VG_(memset) to get into infinite recursion.
-AM_CFLAGS_BASE = \
+AM_CFLAGS_BASE = -fanalyzer \
-O2 -g \
-Wall \
-Wmissing-prototypes \
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug analyzer/99854] gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer
2021-03-31 18:07 [Bug analyzer/99854] New: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer jseward at acm dot org
@ 2021-03-31 18:28 ` dmalcolm at gcc dot gnu.org
2021-03-31 18:37 ` jseward at acm dot org
1 sibling, 0 replies; 3+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2021-03-31 18:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this (and for valgrind!)
Looks like a dup of bug 98599.
*** This bug has been marked as a duplicate of bug 98599 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug analyzer/99854] gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer
2021-03-31 18:07 [Bug analyzer/99854] New: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer jseward at acm dot org
2021-03-31 18:28 ` [Bug analyzer/99854] " dmalcolm at gcc dot gnu.org
@ 2021-03-31 18:37 ` jseward at acm dot org
1 sibling, 0 replies; 3+ messages in thread
From: jseward at acm dot org @ 2021-03-31 18:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854
jseward at acm dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |FIXED
--- Comment #2 from jseward at acm dot org ---
Thanks for the analyzer! I would add (not that it's relevant to this report)
that anecdotally, it seems to use way less memory than when I tested it some
months back. Maybe only 1/4 as much. A big improvement.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-03-31 18:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-31 18:07 [Bug analyzer/99854] New: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer jseward at acm dot org
2021-03-31 18:28 ` [Bug analyzer/99854] " dmalcolm at gcc dot gnu.org
2021-03-31 18:37 ` jseward at acm dot org
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).