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 ipa/101625] [11/12 Regression] ICE in modref_tree<int>::merge with LTO and -m32 since r11-3825-g71dbabccbfb295c8
Date: Thu, 05 Aug 2021 11:43:34 +0000 [thread overview]
Message-ID: <bug-101625-4-tqcR8Gv5Zn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101625-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101625
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Crashes due to:
│ 3120 if (!ignore_stores)
│ 3121 {
│ 3122 if (to_info && callee_info)
│ >3123 to_info->stores->merge (callee_info->stores,
&parm_map);
where to_info->stores == NULL. It's likely related to partial linking.
@Honza?
next prev parent reply other threads:[~2021-08-05 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:45 [Bug lto/101625] New: ICE in modref_tree<int>::merge with LTO and -m32 tonyb at cybernetics dot com
2021-07-27 11:03 ` [Bug ipa/101625] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-07-28 7:07 ` rguenth at gcc dot gnu.org
2021-08-02 14:07 ` [Bug ipa/101625] [11/12 Regression] ICE in modref_tree<int>::merge with LTO and -m32 since r11-3825-g71dbabccbfb295c8 marxin at gcc dot gnu.org
2021-08-05 11:43 ` marxin at gcc dot gnu.org [this message]
2022-04-21 7:50 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` [Bug ipa/101625] [11/12/13/14 " jakub 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-101625-4-tqcR8Gv5Zn@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).