public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/96291] [10/11 Regression] -flto fails as "internal compiler error: Segmentation fault" during IPA pass: cp incall_for_symbol_thunks_and_aliases() Date: Mon, 27 Jul 2020 12:43:17 +0000 [thread overview] Message-ID: <bug-96291-4-nmNh4yy0jM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96291-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96291 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jamborm at gcc dot gnu.org |slyfox at inbox dot ru --- Comment #8 from Martin Jambor <jamborm at gcc dot gnu.org> --- Sergei's patch is correct (I just suggested to write the condition differently).
next prev parent reply other threads:[~2020-07-27 12:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-22 22:41 [Bug lto/96291] New: " slyfox at inbox dot ru 2020-07-23 6:00 ` [Bug ipa/96291] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-23 9:08 ` marxin at gcc dot gnu.org 2020-07-23 10:10 ` jamborm at gcc dot gnu.org 2020-07-24 12:25 ` romain.geissler at amadeus dot com 2020-07-24 18:08 ` slyfox at inbox dot ru 2020-07-25 11:54 ` slyfox at inbox dot ru 2020-07-25 14:09 ` slyfox at inbox dot ru 2020-07-25 18:37 ` slyfox at inbox dot ru 2020-07-27 12:43 ` jamborm at gcc dot gnu.org [this message] 2020-07-28 22:31 ` cvs-commit at gcc dot gnu.org 2020-08-12 17:11 ` [Bug ipa/96291] [10 Regression] -flto fails as ICE " marxin at gcc dot gnu.org 2020-08-12 17:40 ` cvs-commit at gcc dot gnu.org 2020-08-12 17:43 ` 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-96291-4-nmNh4yy0jM@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).