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/105012] [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking Date: Tue, 22 Mar 2022 10:37:00 +0000 [thread overview] Message-ID: <bug-105012-4-S9ehyr0bHJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105012-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- Created attachment 52661 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52661&action=edit ltrans object file I have a small LTRANS reproducer: $ ./lto1 -fltrans /home/marxin/Programming/testcases/wrf_r.ltrans.o Reading object files: /home/marxin/Programming/testcases/wrf_r.ltrans.o {GC 2365k} {heap 1168k} Reading the symbol table: Merging declarations: {GC 2414k} {heap 1168k} Reading summaries: {GC 2414k} {heap 1168k} {GC 2414k} {heap 1168k} {GC 2414k} {heap 1168k} {GC 2414k} {heap 1168k} <cp> {GC 2422k} {heap 1168k} {GC 2422k} {heap 1168k} {GC 2422k} {heap 1168k} {GC 2422k} {heap 1168k} {GC 2422k} {heap 1168k} <modref> {GC 2426k} {heap 1168k} {GC 2426k} {heap 1168k} <static-var> {GC 2426k} {heap 1168k} {GC 2426k} {heap 1168k} {GC 2426k} {heap 1168k} {GC 2426k} in:q.4.lto_priv.0 in:p.5.lto_priv.0 in:d.6.lto_priv.0 in:c.7.lto_priv.0 in:b.8.lto_priv.0 in:a.9.lto_priv.0 in:supersat.2.lto_priv.0Reading function bodies: Performing interprocedural optimizations Assembling functions: <simdclone> {heap 1168k} dropmixnuc.constprop in:__ndrop_MOD_dropmixnuc in:__error_function_MOD_calerf_r8 in:__error_function_MOD_derf in:__module_cam_support_MOD_endrun in:wrf_message_ in:wrf_error_fatal_ in:__module_cam_support_MOD_endrun.part.0 in:__ndrop_MOD_loadaer in:__ndrop_MOD_ccncalc in:__module_cam_support_MOD_outfld {GC madv_dontneed 264k} {GC 6209k -> 3650k} {GC madv_dontneed 652k} {GC 5337k -> 3807k}during GIMPLE pass: ifcvt ../../../../home/marxin/Programming/cpu2017/benchspec/CPU/521.wrf_r/build/build_peak_gcc-m64.0001/module_cam_mp_ndrop.fppized.f90: In function ‘dropmixnuc.constprop’: ../../../../home/marxin/Programming/cpu2017/benchspec/CPU/521.wrf_r/build/build_peak_gcc-m64.0001/module_cam_mp_ndrop.fppized.f90:33:27: internal compiler error: Segmentation fault 0x135c4fb crash_signal /home/marxin/Programming/gcc/gcc/toplev.cc:322 0x7ffff78b93cf ??? /usr/src/debug/glibc-2.35-2.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0xb02a60 tree_check(tree_node*, char const*, int, char const*, tree_code) /home/marxin/Programming/gcc/gcc/tree.h:3450 0x15369e3 first_imm_use_stmt /home/marxin/Programming/gcc/gcc/ssa-iterators.h:931 0x15390e6 dse_classify_store(ao_ref*, gimple*, bool, simple_bitmap_def*, bool*, tree_node*) /home/marxin/Programming/gcc/gcc/tree-ssa-dse.cc:954 0x141afe1 ifcvt_local_dce /home/marxin/Programming/gcc/gcc/tree-if-conv.cc:3154 0x141b89f tree_if_conversion(loop*, vec<gimple*, va_heap, vl_ptr>*) /home/marxin/Programming/gcc/gcc/tree-if-conv.cc:3383 0x141bb02 execute /home/marxin/Programming/gcc/gcc/tree-if-conv.cc:3461 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Richi: Can you please debug this?
next prev parent reply other threads:[~2022-03-22 10:37 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-22 8:54 [Bug lto/105012] New: " tnfchris at gcc dot gnu.org 2022-03-22 9:36 ` [Bug lto/105012] " marxin at gcc dot gnu.org 2022-03-22 10:21 ` rguenth at gcc dot gnu.org 2022-03-22 10:23 ` rguenth at gcc dot gnu.org 2022-03-22 10:37 ` marxin at gcc dot gnu.org [this message] 2022-03-22 10:52 ` rguenth at gcc dot gnu.org 2022-03-22 10:53 ` [Bug lto/105012] [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9 marxin at gcc dot gnu.org 2022-03-22 10:58 ` marxin at gcc dot gnu.org 2022-03-22 11:06 ` [Bug fortran/105012] " rguenth at gcc dot gnu.org 2022-03-22 11:09 ` marxin at gcc dot gnu.org 2022-03-22 11:11 ` rguenth at gcc dot gnu.org 2022-03-22 11:18 ` rguenth at gcc dot gnu.org 2022-03-22 11:20 ` rguenth at gcc dot gnu.org 2022-03-22 11:31 ` rguenth at gcc dot gnu.org 2022-03-22 13:05 ` cvs-commit at gcc dot gnu.org 2022-03-22 13:07 ` rguenth at gcc dot gnu.org 2022-05-06 8:33 ` [Bug fortran/105012] [12/13 " jakub at gcc dot gnu.org 2022-08-24 19:36 ` anlauf at gcc dot gnu.org 2022-08-24 20:34 ` anlauf at gcc dot gnu.org 2022-08-25 6:13 ` rguenth at gcc dot gnu.org 2022-08-25 6:18 ` rguenth at gcc dot gnu.org 2022-08-25 19:50 ` mikael at gcc dot gnu.org 2022-08-25 19:55 ` anlauf at gcc dot gnu.org 2022-08-25 19:57 ` anlauf at gcc dot gnu.org 2022-08-25 20:06 ` mikael at gcc dot gnu.org 2022-08-25 20:30 ` anlauf at gcc dot gnu.org 2022-08-25 20:40 ` mikael at gcc dot gnu.org 2022-08-25 20:47 ` anlauf at gcc dot gnu.org 2022-08-25 21:19 ` mikael at gcc dot gnu.org 2022-08-25 21:31 ` anlauf at gcc dot gnu.org 2022-08-28 10:27 ` mikael at gcc dot gnu.org 2022-09-02 19:04 ` mikael at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-10-10 20:04 ` cvs-commit at gcc dot gnu.org 2022-10-10 20:53 ` cvs-commit at gcc dot gnu.org 2022-10-12 12:34 ` cvs-commit at gcc dot gnu.org 2022-10-12 12:42 ` mikael 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-105012-4-S9ehyr0bHJ@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).