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/109987] New: ICE in in rs6000_emit_le_vsx_store on ppc64le with -Ofast -mno-power8-vector
Date: Fri, 26 May 2023 12:05:00 +0000	[thread overview]
Message-ID: <bug-109987-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109987
           Summary: ICE in in rs6000_emit_le_vsx_store on ppc64le with
                    -Ofast -mno-power8-vector
           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
  Target Milestone: ---
              Host: x86_64-linux
            Target: ppc64le-linux-gnu

With a cross compiler (revision r14-1248-gd156c605420023)
configured with:

/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/configure
--enable-languages=c,c++,fortran,rust,m2 --disable-bootstrap
--disable-libsanitizer --disable-multilib --enable-checking=release
--prefix=/home/worker/cross --target=ppc64le-linux-gnu
--with-as=/usr/bin/powerpc64le-suse-linux-as

and our existing testcase gcc/testsuite/gcc.target/powerpc/pr102347.c, running
it as

~/cross/bin/ppc64le-linux-gnu-gcc
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/pr102347.c
-Ofast -mno-power8-vector

Results in ICE:

during RTL pass: split2
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/pr102347.c:
In function ‘main’:
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/pr102347.c:15:1:
internal compiler error: in rs6000_emit_le_vsx_store, at
config/rs6000/rs6000.cc:10547
   15 | }
      | ^
0x63d7f7 rs6000_emit_le_vsx_store(rtx_def*, rtx_def*, machine_mode)
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/config/rs6000/rs6000.cc:10547
0x1293d37 gen_movv16qi(rtx_def*, rtx_def*)
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/config/rs6000/vector.md:161
0x8938b7 rtx_insn* insn_gen_fn::operator()<rtx_def*, rtx_def*>(rtx_def*,
rtx_def*) const
        /home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/recog.h:407
0x8938b7 emit_move_ccmode
        /home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/expr.cc:4043
0x8938b7 emit_move_insn_1(rtx_def*, rtx_def*)
        /home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/expr.cc:4188
0x893c9d emit_move_insn(rtx_def*, rtx_def*)
        /home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/expr.cc:4339
0x12c925b gen_split_707(rtx_insn*, rtx_def**)
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/config/rs6000/mma.md:498
0x136dcda split_14
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/config/rs6000/mma.md:494
0x136dcda split_18
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/config/rs6000/rs6000.md:471
0x861170 try_split(rtx_def*, rtx_insn*, int)
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/emit-rtl.cc:3804
0xb5af71 split_insn
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/recog.cc:3385
0xb60221 split_all_insns()
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/recog.cc:3489
0xb60308 execute
       
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/recog.cc:4413

             reply	other threads:[~2023-05-26 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 12:05 jamborm at gcc dot gnu.org [this message]
2023-05-29  1:29 ` [Bug target/109987] " linkw at gcc dot gnu.org
2024-01-09  2:07 ` linkw at gcc dot gnu.org
2024-01-10  8:13 ` linkw at gcc dot gnu.org
2024-03-26  6:23 ` 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-109987-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: 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).