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: Mon, 02 Aug 2021 14:07:30 +0000 [thread overview] Message-ID: <bug-101625-4-G5UErlX6s8@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 ---------------------------------------------------------------------------- Last reconfirmed| |2021-08-02 Summary|[11/12 Regression] ICE in |[11/12 Regression] ICE in |modref_tree<int>::merge |modref_tree<int>::merge |with LTO and -m32 |with LTO and -m32 since | |r11-3825-g71dbabccbfb295c8 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed, started with r11-3825-g71dbabccbfb295c8. Reduced test-case: $ cat ice.i typedef enum { XXH_OK } XXH_errorcode; struct XXH64_state_s {}; struct XXH32_state_s {}; void XXH_free(); XXH_errorcode XXH32_freeState(struct XXH32_state_s *statePtr) { XXH_free(statePtr); return XXH_OK; } XXH_errorcode XXH64_freeState(struct XXH64_state_s *statePtr) { XXH_free(statePtr); return XXH_OK; } $ gcc ice.i -Os -ffat-lto-objects -nostdlib -nostdlib -Wl,-r,-d -flto during IPA pass: inline lto1: internal compiler error: Segmentation fault 0xd6ecba crash_signal /home/marxin/Programming/gcc/gcc/toplev.c:328 0x7ffff786239f ??? ../sysdeps/unix/sysv/linux/sigaction.c:10 0xb4b57b modref_tree<int>::merge(modref_tree<int>*, vec<modref_parm_map, va_heap, vl_ptr>*) /home/marxin/Programming/gcc/gcc/ipa-modref-tree.h:420 0xb4008a ipa_merge_modref_summary_after_inlining(cgraph_edge*) /home/marxin/Programming/gcc/gcc/ipa-modref.c:3123 0xb3393b inline_call(cgraph_edge*, bool, vec<cgraph_edge*, va_heap, vl_ptr>*, int*, bool, bool*) /home/marxin/Programming/gcc/gcc/ipa-inline-transform.c:503 0x18b4e1c inline_small_functions /home/marxin/Programming/gcc/gcc/ipa-inline.c:2245 0x18b4e1c ipa_inline /home/marxin/Programming/gcc/gcc/ipa-inline.c:2726 0x18b4e1c execute /home/marxin/Programming/gcc/gcc/ipa-inline.c:3125 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. lto-wrapper: fatal error: gcc returned 1 exit status compilation terminated. /usr/bin/ld: fatal error: lto-wrapper failed collect2: error: ld returned 1 exit status
next prev parent reply other threads:[~2021-08-02 14:07 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 ` marxin at gcc dot gnu.org [this message] 2021-08-05 11:43 ` [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 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-G5UErlX6s8@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).