public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114885] RISC-V: ICE of unrecog insn when graphite for both the c/c++ and fortran
Date: Mon, 29 Apr 2024 07:48:43 +0000	[thread overview]
Message-ID: <bug-114885-4-uuDulqLSA9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114885-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pan Li <panli@gcc.gnu.org>:

https://gcc.gnu.org/g:add51a2514a39978dc66976a8974f8435c86168f

commit r15-45-gadd51a2514a39978dc66976a8974f8435c86168f
Author: Pan Li <pan2.li@intel.com>
Date:   Sat Apr 27 20:24:04 2024 +0800

    RISC-V: Fix ICE for legitimize move on subreg const_poly_int [PR114885]

    When we build with isl, there will be a ICE for graphite in both
    the c/c++ and fortran.  The legitimize move cannot take care of
    below rtl.

    (set (subreg:DI (reg:TI 237) 8) (subreg:DI (const_poly_int:TI [4, 2]) 8))

    Then we will have ice similar to below:

    internal compiler error: in extract_insn, at recog.cc:2812.

    This patch would like to take care of the above rtl.  Given the value of
    const_poly_int can hardly excceed the max of int64,  we can simply
    consider the highest 8 bytes of TImode is zero and then set the dest
    to (const_int 0).

    The below test cases are fixed by this PATCH.

    C:
    FAIL: gcc.dg/graphite/pr111878.c (internal compiler error: in
    extract_insn, at recog.cc:2812)
    FAIL: gcc.dg/graphite/pr111878.c (test for excess errors)

    Fortran:
    FAIL: gfortran.dg/graphite/vect-pr40979.f90   -O  (internal compiler
    error: in extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr29832.f90   -O3 -fomit-frame-pointer
    -funroll-loops -fpeel-loops -ftracer -finline-functions  (internal
    compiler error: in extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr29581.f90   -O3 -g  (test for excess
    errors)
    FAIL: gfortran.dg/graphite/pr14741.f90   -O  (test for excess errors)
    FAIL: gfortran.dg/graphite/pr29581.f90   -O3 -fomit-frame-pointer
    -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for
    excess errors)
    FAIL: gfortran.dg/graphite/vect-pr40979.f90   -O  (test for excess
    errors)
    FAIL: gfortran.dg/graphite/id-27.f90   -O  (internal compiler error: in
    extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr29832.f90   -O3 -g  (internal compiler
    error: in extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr29832.f90   -O3 -g  (test for excess
    errors)
    FAIL: gfortran.dg/graphite/id-27.f90   -O  (test for excess errors)
    FAIL: gfortran.dg/graphite/pr29832.f90   -O3 -fomit-frame-pointer
    -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for
    excess errors)
    FAIL: gfortran.dg/graphite/pr29581.f90   -O3 -fomit-frame-pointer
    -funroll-loops -fpeel-loops -ftracer -finline-functions  (internal
    compiler error: in extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr14741.f90   -O  (internal compiler error:
    in extract_insn, at recog.cc:2812)
    FAIL: gfortran.dg/graphite/pr29581.f90   -O3 -g  (internal compiler
    error: in extract_insn, at recog.cc:2812)

    The below test suites are passed for this patch:
    * The rv64gcv fully regression test.
    * The rv64gc fully regression test.

    Try to write some RTL code for test but not works well according to
    existing test cases.  Thus, take above as test cases.  Please note
    graphite require the gcc build with isl.

            PR target/114885

    gcc/ChangeLog:

            * config/riscv/riscv.cc (riscv_legitimize_subreg_const_poly_move):
New
            func impl to take care of (const_int_poly:TI 8).
            (riscv_legitimize_move): Handle subreg is const_int_poly,

    Signed-off-by: Pan Li <pan2.li@intel.com>

  parent reply	other threads:[~2024-04-29  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  6:43 [Bug c/114885] New: " pan2.li at intel dot com
2024-04-29  6:45 ` [Bug c/114885] " kito at gcc dot gnu.org
2024-04-29  7:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-29  8:31 ` [Bug target/114885] " cvs-commit at gcc dot gnu.org
2024-04-29 15:12 ` law 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-114885-4-uuDulqLSA9@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).