public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "max.aehle at scicomp dot uni-kl.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109276] New: ICE: in assign_stack_local_1, at function.cc:429 with -mpreferred-stack-boundary=2 Date: Fri, 24 Mar 2023 17:31:04 +0000 [thread overview] Message-ID: <bug-109276-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109276 Bug ID: 109276 Summary: ICE: in assign_stack_local_1, at function.cc:429 with -mpreferred-stack-boundary=2 Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: max.aehle at scicomp dot uni-kl.de Target Milestone: --- Created attachment 54745 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54745&action=edit verbose output, preprocessed source, .i and .s file Compiling the attached bug.c with GCC 12.2.0 via gcc -m32 -O0 -c bug.c -mpreferred-stack-boundary=2 prints during RTL pass: split1 bug.c: In function 'fun': bug.c:23:1: internal compiler error: in assign_stack_local_1, at function.cc:429 23 | } | ^ 0x6d3b9b assign_stack_local_1(machine_mode, poly_int<1u, long>, int, int) /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/function.cc:429 0xf81d50 assign_386_stack_local(machine_mode, ix86_stack_slot) /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/config/i386/i386.cc:16558 0x13bdd87 gen_split_65(rtx_insn*, rtx_def**) /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/config/i386/i386.md:5471 0x17d3e0a split_insns(rtx_def*, rtx_insn*) /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/config/i386/i386.md:15646 0x9295fe try_split(rtx_def*, rtx_insn*, int) /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/emit-rtl.cc:3795 0xc01fb1 split_insn /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/recog.cc:3384 0xc072f2 split_all_insns() /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/recog.cc:3488 0xc073e8 execute /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/gcc/recog.cc:4406 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. We have attached: - the stdout/stderr output with the additional flag -v, - the preprocessed source produced with -freport-bug, - the files bug.i and bug.s produced with -save-temps. The GCC 12.2.0 build was configured only with a --prefix option. gcc -v shows Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/ramdisk/aehle/gcc/gcc-install/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /ramdisk/aehle/gcc/gcc-obj/../gcc-12.2.0/configure --prefix=/ramdisk/aehle/gcc/gcc-obj/../gcc-install Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.2.0 (GCC) uname -a says "Linux <hostname> 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 GNU/Linux". /proc/cpuinfo shows a list of 96 cores with the model name "AMD EPYC 7F72 24-Core Processor". All of the above commands were executed in a Singularity container based on Debian 11.3. The source file is a minimal example condensed from Valgrind's m_libcbase.c.
next reply other threads:[~2023-03-24 17:31 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 17:31 max.aehle at scicomp dot uni-kl.de [this message] 2023-03-24 17:32 ` [Bug rtl-optimization/109276] " max.aehle at scicomp dot uni-kl.de 2023-03-24 17:32 ` max.aehle at scicomp dot uni-kl.de 2023-03-24 17:33 ` max.aehle at scicomp dot uni-kl.de 2023-03-24 17:34 ` max.aehle at scicomp dot uni-kl.de 2023-03-24 17:35 ` max.aehle at scicomp dot uni-kl.de 2023-03-24 17:38 ` max.aehle at scicomp dot uni-kl.de 2023-03-24 17:47 ` [Bug target/109276] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2023-03-24 17:56 ` jakub at gcc dot gnu.org 2023-03-24 18:03 ` pinskia at gcc dot gnu.org 2023-03-24 18:09 ` pinskia at gcc dot gnu.org 2023-03-24 18:32 ` hjl.tools at gmail dot com 2023-03-27 7:02 ` rguenth at gcc dot gnu.org 2023-03-27 15:09 ` jakub at gcc dot gnu.org 2023-03-27 15:13 ` jakub at gcc dot gnu.org 2023-03-27 15:36 ` jakub at gcc dot gnu.org 2023-03-27 16:18 ` jakub at gcc dot gnu.org 2023-03-27 19:15 ` ubizjak at gmail dot com 2023-03-27 19:22 ` jakub at gcc dot gnu.org 2023-03-27 20:14 ` ubizjak at gmail dot com 2023-03-28 8:43 ` cvs-commit at gcc dot gnu.org 2023-03-28 8:45 ` [Bug target/109276] [11/12 " jakub at gcc dot gnu.org 2023-04-18 7:15 ` cvs-commit at gcc dot gnu.org 2023-04-18 7:20 ` [Bug target/109276] [11 " jakub at gcc dot gnu.org 2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org 2023-05-03 10:46 ` 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-109276-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).