public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113133] New: [14 Regression] ICE: SIGSEGV in mark_label_nuses(rtx_def*) (emit-rtl.cc:3896) with -O -fno-tree-ter -mavx512f -march=barcelona Date: Mon, 25 Dec 2023 11:09:27 +0000 [thread overview] Message-ID: <bug-113133-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113133 Bug ID: 113133 Summary: [14 Regression] ICE: SIGSEGV in mark_label_nuses(rtx_def*) (emit-rtl.cc:3896) with -O -fno-tree-ter -mavx512f -march=barcelona Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 56931 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56931&action=edit reduced testcase I am observing these kind of SEGSEGV, -O -fno-tree-ter -mavx512f -march="some older amd64" seems to be the common set of flags. Up to try_split() seems to be the common backtrace. Compiler output: $ x86_64-pc-linux-gnu-gcc -O -fno-tree-ter -mavx512f -march=barcelona testcase.c -wrapper valgrind,-q ==3147== Invalid read of size 1 ==3147== at 0x1079841: mark_label_nuses(rtx_def*) (emit-rtl.cc:3896) ==3147== by 0x10798C4: mark_label_nuses(rtx_def*) (emit-rtl.cc:3904) ==3147== by 0x10798C4: mark_label_nuses(rtx_def*) (emit-rtl.cc:3904) ==3147== by 0x10798C4: mark_label_nuses(rtx_def*) (emit-rtl.cc:3904) ==3147== by 0x108057A: try_split(rtx_def*, rtx_insn*, int) (emit-rtl.cc:4093) ==3147== by 0x144AB28: split_insn(rtx_insn*) (recog.cc:3405) ==3147== by 0x14519C5: split_all_insns() (recog.cc:3509) ==3147== by 0x1451AE8: (anonymous namespace)::pass_split_all_insns::execute(function*) (recog.cc:4433) ==3147== by 0x13C9A6A: execute_one_pass(opt_pass*) (passes.cc:2646) ==3147== by 0x13CA35F: execute_pass_list_1(opt_pass*) (passes.cc:2755) ==3147== by 0x13CA371: execute_pass_list_1(opt_pass*) (passes.cc:2756) ==3147== by 0x13CA371: execute_pass_list_1(opt_pass*) (passes.cc:2756) ==3147== Address 0x2 is not stack'd, malloc'd or (recently) free'd ==3147== during RTL pass: split2 testcase.c: In function 'foo0': testcase.c:68:1: internal compiler error: Segmentation fault 68 | } | ^ 0x150b4af crash_signal /repo/gcc-trunk/gcc/toplev.cc:316 0x1079841 mark_label_nuses /repo/gcc-trunk/gcc/emit-rtl.cc:3896 0x10798c4 mark_label_nuses /repo/gcc-trunk/gcc/emit-rtl.cc:3904 0x10798c4 mark_label_nuses /repo/gcc-trunk/gcc/emit-rtl.cc:3904 0x10798c4 mark_label_nuses /repo/gcc-trunk/gcc/emit-rtl.cc:3904 0x108057a try_split(rtx_def*, rtx_insn*, int) /repo/gcc-trunk/gcc/emit-rtl.cc:4093 0x144ab28 split_insn /repo/gcc-trunk/gcc/recog.cc:3405 0x14519c5 split_all_insns() /repo/gcc-trunk/gcc/recog.cc:3509 0x1451ae8 execute /repo/gcc-trunk/gcc/recog.cc:4433 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. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-6825-20231224193009-ga657c7e3518-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-6825-20231224193009-ga657c7e3518-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20231224 (experimental) (GCC)
next reply other threads:[~2023-12-25 11:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-25 11:09 zsojka at seznam dot cz [this message] 2023-12-28 19:36 ` [Bug target/113133] " ubizjak at gmail dot com 2023-12-28 19:37 ` ubizjak at gmail dot com 2023-12-28 20:02 ` ubizjak at gmail dot com 2023-12-28 20:10 ` ubizjak at gmail dot com 2023-12-29 2:08 ` haochen.jiang at intel dot com 2023-12-29 2:31 ` haochen.jiang at intel dot com 2023-12-29 7:35 ` haochen.jiang at intel dot com 2023-12-29 8:16 ` ubizjak at gmail dot com 2023-12-29 8:53 ` cvs-commit at gcc dot gnu.org 2023-12-29 8:57 ` ubizjak at gmail dot com 2024-01-02 6:39 ` haochen.jiang at intel dot com
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-113133-4@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).