public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111225] New: ICE in curr_insn_transform, unable to generate reloads for xor, since r14-2447-g13c556d6ae84be Date: Tue, 29 Aug 2023 13:01:23 +0000 [thread overview] Message-ID: <bug-111225-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111225 Bug ID: 111225 Summary: ICE in curr_insn_transform, unable to generate reloads for xor, since r14-2447-g13c556d6ae84be Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org CC: crazylht at gmail dot com, fkastl at suse dot cz Target Milestone: --- Host: x86_64-linux Target: x86_64-linux On GCC 14 development master, since revision r14-2447-g13c556d6ae84be, I get an ICE when compiling our testcase gcc/testsuite/gcc.target/i386/avx-vptest-5.c with options -fsanitize=thread -O1 -mforce-drap -mavx512cd: $ ~/gcc/small/inst/bin/gcc /home/mjambor/gcc/trunk/src/gcc/testsuite/gcc.target/i386/avx-vptest-5.c -fsanitize=thread -O1 -mforce-drap -mavx512cd /home/mjambor/gcc/trunk/src/gcc/testsuite/gcc.target/i386/avx-vptest-5.c: In function ‘foo’: /home/mjambor/gcc/trunk/src/gcc/testsuite/gcc.target/i386/avx-vptest-5.c:10:1: error: unable to generate reloads for: 10 | } | ^ (insn 11 10 12 2 (set (reg:V4DI 91) (xor:V4DI (mem/c:V4DI (plus:DI (reg/f:DI 19 frame) (const_int -80 [0xffffffffffffffb0])) [1 %sfp+-64 S32 A256]) (const_vector:V4DI [ (const_int -1 [0xffffffffffffffff]) repeated x4 ]))) "/home/mjambor/gcc/trunk/src/gcc/testsuite/gcc.target/i386/avx-vptest-5.c":8:19 6853 {*one_cmplv4di2} (expr_list:REG_DEAD (reg/v:V4DI 89 [ y ]) (nil))) during RTL pass: reload /home/mjambor/gcc/trunk/src/gcc/testsuite/gcc.target/i386/avx-vptest-5.c:10:1: internal compiler error: in curr_insn_transform, at lra-constraints.cc:4259 0x7cd910 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /home/mjambor/gcc/small/src/gcc/rtl-error.cc:108 0x7a42c0 curr_insn_transform /home/mjambor/gcc/small/src/gcc/lra-constraints.cc:4259 0xdcda7e lra_constraints(bool) /home/mjambor/gcc/small/src/gcc/lra-constraints.cc:5430 0xdb99c2 lra(_IO_FILE*) /home/mjambor/gcc/small/src/gcc/lra.cc:2396 0xd715f1 do_reload /home/mjambor/gcc/small/src/gcc/ira.cc:5967 0xd715f1 execute /home/mjambor/gcc/small/src/gcc/ira.cc:6153 Please submit a full bug report, with preprocessed source (by using -freport-bug). As noted earlier, I have bisected this down to: commit 13c556d6ae84be3ee2bc245a56eafa58221de86a (HEAD) Author: liuhongt <hongtao.liu@intel.com> Date: Thu Jun 29 14:25:28 2023 +0800 Break false dependence for vpternlog by inserting vpxor or setting constraint of input operand to '0' False dependency happens when destination is only updated by pternlog. There is no false dependency when destination is also used in source. So either a pxor should be inserted, or input operand should be set with constraint '0'. gcc/ChangeLog: PR target/110438 PR target/110202 * config/i386/predicates.md (int_float_vector_all_ones_operand): New predicate. * config/i386/sse.md (*vmov<mode>_constm1_pternlog_false_dep): New define_insn. (*<avx512>_cvtmask2<ssemodesuffix><mode>_pternlog_false_dep): Ditto. (*<avx512>_cvtmask2<ssemodesuffix><mode>_pternlog_false_dep): Ditto. (*<avx512>_cvtmask2<ssemodesuffix><mode>): Adjust to define_insn_and_split to avoid false dependence. (*<avx512>_cvtmask2<ssemodesuffix><mode>): Ditto. (<mask_codefor>one_cmpl<mode>2<mask_name>): Adjust constraint of operands 1 to '0' to avoid false dependence. (*andnot<mode>3): Ditto. (iornot<mode>3): Ditto. (*<nlogic><mode>3): Ditto.
next reply other threads:[~2023-08-29 13:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-29 13:01 jamborm at gcc dot gnu.org [this message] 2023-08-30 2:12 ` [Bug target/111225] " crazylht at gmail dot com 2023-08-30 2:16 ` crazylht at gmail dot com 2023-08-30 21:31 ` vmakarov at gcc dot gnu.org 2023-09-07 14:04 ` cvs-commit at gcc dot gnu.org 2023-11-30 10:46 ` liuhongt 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-111225-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).