public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99422] New: [11 Regression] ICE in extract_constrain_insn building glibc pthread_create Date: Sat, 06 Mar 2021 01:31:42 +0000 [thread overview] Message-ID: <bug-99422-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422 Bug ID: 99422 Summary: [11 Regression] ICE in extract_constrain_insn building glibc pthread_create Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jsm28 at gcc dot gnu.org CC: vmakarov at gcc dot gnu.org Target Milestone: --- Target: i686-*-linux-gnu Created attachment 50314 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50314&action=edit preprocessed source Commit 9105757a59b890194ebf5b4fcbacd58db34ef332 ("[PR99378] LRA: Skip decomposing address for asm insn operand with unknown constraint.") introduced the following ICE building glibc for i686-linux-gnu. Tested with an x86_64 compiler; compile the attached .i file with the following options: -m32 -march=i686 -O2 -pg -S In file included from pthread_create.c:59: allocatestack.c: In function '__nptl_setxid': allocatestack.c:1173:1: error: unrecognizable insn: (insn 103 534 535 21 (parallel [ (set (mem/v:SI (plus:SI (mem/f/c:SI (plus:SI (reg/f:SI 6 bp) (const_int 8 [0x8])) [85 cmdp+0 S4 A32]) (const_int 16 [0x10])) [5 cmdp_52(D)->cntr+0 S4 A32]) (asm_operands/v:SI ("lock;incl %0") ("=m") 0 [ (mem/v:SI (plus:SI (reg:SI 0 ax [208]) (const_int 16 [0x10])) [5 cmdp_52(D)->cntr+0 S4 A32]) (const_int 12 [0xc]) ] [ (asm_input:SI ("m") allocatestack.c:1036) (asm_input:SI ("i") allocatestack.c:1036) ] [] allocatestack.c:1036)) (clobber (reg:CC 17 flags)) ]) "allocatestack.c":1036:47 -1 (nil)) during RTL pass: reload allocatestack.c:1173:1: internal compiler error: in extract_constrain_insn, at recog.c:2670 0x63ae76 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /scratch/jmyers/glibc/many11/src/gcc/gcc/rtl-error.c:108 0x63ae92 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /scratch/jmyers/glibc/many11/src/gcc/gcc/rtl-error.c:116 0xd1149d extract_constrain_insn(rtx_insn*) /scratch/jmyers/glibc/many11/src/gcc/gcc/recog.c:2670 0xbec6a7 check_rtl /scratch/jmyers/glibc/many11/src/gcc/gcc/lra.c:2087 0xbf14ac lra(_IO_FILE*) /scratch/jmyers/glibc/many11/src/gcc/gcc/lra.c:2505 0xba1489 do_reload /scratch/jmyers/glibc/many11/src/gcc/gcc/ira.c:5827 0xba1489 execute /scratch/jmyers/glibc/many11/src/gcc/gcc/ira.c:6013 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.
next reply other threads:[~2021-03-06 1:31 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-06 1:31 jsm28 at gcc dot gnu.org [this message] 2021-03-06 9:51 ` [Bug target/99422] " jakub at gcc dot gnu.org 2021-03-06 9:51 ` jakub at gcc dot gnu.org 2021-03-06 10:08 ` jakub at gcc dot gnu.org 2021-03-06 18:57 ` dcb314 at hotmail dot com 2021-03-07 2:27 ` pinskia at gcc dot gnu.org 2021-03-07 2:28 ` pinskia at gcc dot gnu.org 2021-03-07 19:01 ` vmakarov at gcc dot gnu.org 2021-03-07 19:49 ` vmakarov at gcc dot gnu.org 2021-03-07 20:34 ` pinskia at gcc dot gnu.org 2021-03-07 21:00 ` pinskia at gcc dot gnu.org 2021-03-08 14:26 ` cvs-commit at gcc dot gnu.org 2021-03-08 14:31 ` vmakarov at gcc dot gnu.org 2021-03-08 18:53 ` ro at gcc dot gnu.org 2021-03-08 18:58 ` vmakarov at gcc dot gnu.org 2021-03-08 19:05 ` vmakarov at gcc dot gnu.org 2021-03-08 19:33 ` gerald at pfeifer dot com 2021-03-08 20:45 ` raj.khem at gmail dot com 2021-03-08 21:16 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-03-10 14:06 ` ro at gcc dot gnu.org 2021-03-10 16:10 ` ebotcazou at gcc dot gnu.org 2021-03-10 18:46 ` vmakarov at gcc dot gnu.org 2021-03-10 21:16 ` cvs-commit at gcc dot gnu.org 2021-03-10 21:21 ` vmakarov at gcc dot gnu.org 2021-03-11 9:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-03-11 10:13 ` ebotcazou at gcc dot gnu.org 2021-03-11 19:11 ` vmakarov at gcc dot gnu.org 2021-03-11 21:34 ` vmakarov at gcc dot gnu.org 2021-03-11 23:38 ` ebotcazou at gcc dot gnu.org 2021-03-12 17:52 ` cvs-commit at gcc dot gnu.org 2021-03-16 10:36 ` jakub at gcc dot gnu.org 2021-03-16 19:26 ` jakub at gcc dot gnu.org 2021-03-18 19:59 ` cvs-commit 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-99422-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).