public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/109676] [13/14 regression] ICE in simplify_subreg, at simplify-rtx.cc:7426 when building firefox with -O2 -march=alderlake -g
Date: Sat, 29 Apr 2023 21:05:25 +0000	[thread overview]
Message-ID: <bug-109676-4-k6ZNbnlqhV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109676-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109676

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---

102: (value/u:V1TI 24:24 @0x49b13d8/0x49a15f0) is at (mem/c:V1TI (value/u:DI
13:4290 @0x49b1328/0x49a1438) [0 p+0 S16 A128])
102: (reg:V1TI 20 xmm0 [orig:91 p ] [91]) evaluates to (value/u/f:V1TI 24:24
@0x49b13d8/0x49a15f0)


It is this which is causing the ICE:
(insn 102 110 106 6 (set (reg:V1TI 20 xmm0 [orig:91 p ] [91])
        (mem/c:V1TI (plus:DI (reg/f:DI 7 sp)
                (const_int 32 [0x20])) [0 p+0 S16 A128]))
"/app/example.cpp":26:12 1838 {movv1ti_internal}
     (nil))
(debug_insn 106 102 107 6 (var_location:QI D#3 (mem/c:QI (plus:DI (reg/f:DI 7
sp)
            (const_int 48 [0x30])) [0 p.mIsSome+0 S1 A128]))
"/app/example.cpp":26:12 -1
     (nil))
(debug_insn 107 106 108 6 (var_location:QI tmp$mIsSome (debug_expr:QI D#3))
"/app/example.cpp":26:12 -1
     (nil))

I suspect it is doing a subreg for QI mode of a V1TI reg and simplify_subreg is
ICEing out.

  parent reply	other threads:[~2023-04-29 21:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29  1:29 [Bug rtl-optimization/109676] New: " sjames at gcc dot gnu.org
2023-04-29  2:33 ` [Bug debug/109676] " pinskia at gcc dot gnu.org
2023-04-29  2:48 ` pinskia at gcc dot gnu.org
2023-04-29  4:26 ` sjames at gcc dot gnu.org
2023-04-29 20:22 ` sjames at gcc dot gnu.org
2023-04-29 20:51 ` pinskia at gcc dot gnu.org
2023-04-29 20:51 ` pinskia at gcc dot gnu.org
2023-04-29 20:57 ` pinskia at gcc dot gnu.org
2023-04-29 21:05 ` pinskia at gcc dot gnu.org [this message]
2023-04-29 21:08 ` pinskia at gcc dot gnu.org
2023-04-29 21:56 ` pinskia at gcc dot gnu.org
2023-04-29 23:31 ` [Bug debug/109676] [13/14 regression] ICE in simplify_subreg, at simplify-rtx.cc:7426 when building firefox with -O2 -march=alderlake -g since r13-3378-gf6c168f8c06047 sjames at gcc dot gnu.org
2023-05-01  9:13 ` jakub at gcc dot gnu.org
2023-05-01 11:21 ` jakub at gcc dot gnu.org
2023-05-01 13:01 ` jakub at gcc dot gnu.org
2023-05-02  6:24 ` rguenth at gcc dot gnu.org
2023-05-04  7:37 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:44 ` cvs-commit at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2023-11-06  1:36 ` pinskia 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-109676-4-k6ZNbnlqhV@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: link
Be 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).