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/98078] ICE in cgraph_add_edge_to_call_site_hash, at cgraph.c:698 since r6-1705-gd88511aec7338a93 Date: Thu, 21 Jan 2021 10:02:07 +0000 [thread overview] Message-ID: <bug-98078-4-h0HoABFBGP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98078-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98078 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> --- Actually no, that would be papering over a bigger problem. After looking at the issue a bit more, I proposed a patch on the mailing list: https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563962.html
next prev parent reply other threads:[~2021-01-21 10:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-01 10:09 [Bug ipa/98078] New: " marxin at gcc dot gnu.org 2020-12-01 10:09 ` [Bug ipa/98078] " marxin at gcc dot gnu.org 2020-12-01 10:10 ` marxin at gcc dot gnu.org 2021-01-18 19:21 ` jamborm at gcc dot gnu.org 2021-01-21 10:02 ` jamborm at gcc dot gnu.org [this message] 2021-03-05 16:42 ` cvs-commit at gcc dot gnu.org 2021-03-05 16:54 ` jamborm at gcc dot gnu.org 2021-03-16 15:44 ` cvs-commit at gcc dot gnu.org 2021-03-17 10:35 ` cvs-commit at gcc dot gnu.org 2021-03-17 10:36 ` jamborm 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-98078-4-h0HoABFBGP@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).