public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/107418] lto-dump -gimple-stats ICE Segmentation Fault
Date: Thu, 27 Oct 2022 08:33:53 +0000 [thread overview]
Message-ID: <bug-107418-4-dWMMTfKn83@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107418-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107418
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:ca0220d42e075194ca1341c98a0a9a9f3fd1c719
commit r12-8872-gca0220d42e075194ca1341c98a0a9a9f3fd1c719
Author: Martin Liska <mliska@suse.cz>
Date: Thu Oct 27 10:29:17 2022 +0200
lto: do not load LTO stream for aliases [PR107418]
PR lto/107418
gcc/lto/ChangeLog:
* lto-dump.cc (lto_main): Do not load LTO stream for aliases.
(cherry picked from commit be6c75547385c69706370f4e792b04295f708a5a)
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed for GCC 12/13 releases.
next prev parent reply other threads:[~2022-10-27 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 16:17 [Bug lto/107418] New: lto-dump -gimple-stats " volker.weissmann at gmx dot de
2022-10-26 16:23 ` [Bug lto/107418] " volker.weissmann at gmx dot de
2022-10-27 8:14 ` [Bug lto/107418] lto-dump -gimple-stats ICE " marxin at gcc dot gnu.org
2022-10-27 8:32 ` cvs-commit at gcc dot gnu.org
2022-10-27 8:33 ` marxin at gcc dot gnu.org [this message]
2022-10-27 8:33 ` cvs-commit 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-107418-4-dWMMTfKn83@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).