public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106101] [12/13 Regression] ICE in reg_bitfield_target_p since r12-4428-g147ed0184f403b Date: Thu, 25 Aug 2022 13:02:49 +0000 [thread overview] Message-ID: <bug-106101-4-GgMV1Y0eN6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106101-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106101 --- Comment #21 from Andreas Krebbel <krebbel at gcc dot gnu.org> --- I have committed a patch now which accepts only SUBREGs before reload and then also REGs to deal with how LRA operates right now. I've continued a bit with the patch from Comment 18. It bootstraps on s390x and x86-64. On s390x also the testsuite is clean. However, I see a few failures in the arch specific tests on x86-64. The cases I looked at so far are the result of several peepholes and splitters not being triggered anymore. I've fixed most of them I think but there are also cases where I'm not sure what to do exactly. In case of a matching constraint between a strict_low_part operand and a normal operand. Reload now (with the patch from Comment 18) would remove the subreg on the operand with the matching constraint and would leave it in for the strict_low_part operand. (insn 9 8 16 2 (parallel [ (set (strict_low_part (subreg:QI (reg/v:SI 0 ax [orig:86 a ] [86]) 0)) (and:QI (reg:QI 0 ax [orig:86 a ] [86]) (reg:SI 4 si [92]))) (clobber (reg:CC 17 flags)) ]) "/home/andreas/gcc/gcc/testsuite/gcc.target/i386/pr91188-1a.c":20:10 553 {*andqi_1_slp} (nil)) I think this should be addressed separately. Once we solved it I will adjust the s390x backend again if necessary.
next prev parent reply other threads:[~2022-08-25 13:02 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-27 9:22 [Bug rtl-optimization/106101] New: [12/13 Regression] ICE in reg_bitfield_target_p rguenth at gcc dot gnu.org 2022-06-27 9:22 ` [Bug rtl-optimization/106101] " rguenth at gcc dot gnu.org 2022-06-27 9:22 ` rguenth at gcc dot gnu.org 2022-06-27 9:26 ` rguenth at gcc dot gnu.org 2022-06-27 15:10 ` segher at gcc dot gnu.org 2022-06-28 6:57 ` [Bug target/106101] " rguenth at gcc dot gnu.org 2022-06-28 15:03 ` segher at gcc dot gnu.org 2022-06-28 16:58 ` segher at gcc dot gnu.org 2022-06-29 9:11 ` rguenth at gcc dot gnu.org 2022-06-29 15:48 ` segher at gcc dot gnu.org 2022-07-08 13:56 ` [Bug target/106101] [12/13 Regression] ICE in reg_bitfield_target_p since r12-4428-g147ed0184f403b marxin at gcc dot gnu.org 2022-07-14 10:02 ` krebbel at gcc dot gnu.org 2022-07-19 11:53 ` krebbel at gcc dot gnu.org 2022-08-24 6:46 ` krebbel at gcc dot gnu.org 2022-08-24 11:57 ` segher at gcc dot gnu.org 2022-08-25 12:40 ` cvs-commit at gcc dot gnu.org 2022-08-25 13:02 ` krebbel at gcc dot gnu.org [this message] 2022-08-25 13:55 ` krebbel at gcc dot gnu.org 2022-08-25 15:03 ` segher at gcc dot gnu.org 2023-01-17 15:25 ` [Bug target/106101] [12 " rguenth at gcc dot gnu.org 2023-01-17 15:26 ` rguenth at gcc dot gnu.org 2023-01-23 7:58 ` cvs-commit at gcc dot gnu.org 2023-03-01 13:28 ` rguenth at gcc dot gnu.org 2023-10-10 14:29 ` fw at gcc dot gnu.org 2023-10-10 17:36 ` pinskia at gcc dot gnu.org 2023-10-10 17:39 ` pinskia at gcc dot gnu.org 2023-10-11 6:46 ` fw 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-106101-4-GgMV1Y0eN6@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).