public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jseward at acm dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/99854] gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer Date: Wed, 31 Mar 2021 18:37:37 +0000 [thread overview] Message-ID: <bug-99854-4-go7scinI2W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99854-4@http.gcc.gnu.org/bugzilla/> 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.
prev parent reply other threads:[~2021-03-31 18:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 18:07 [Bug analyzer/99854] New: " 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 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-99854-4-go7scinI2W@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: linkBe 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).