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/113404] ICE: in to_constant, at poly-int.h:588 with -march=rv64gcv -mbig-endian --param=riscv-vector-abi
Date: Tue, 16 Jan 2024 03:20:45 +0000	[thread overview]
Message-ID: <bug-113404-4-eyEmMmqVai@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113404-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 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:5134d3074ad7a462b4c8e2c0bc904b5ba40b7373

commit r14-7271-g5134d3074ad7a462b4c8e2c0bc904b5ba40b7373
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Tue Jan 16 11:04:49 2024 +0800

    RISC-V: Report Sorry when users enable RVV in big-endian mode [PR113404]

    As PR113404 mentioned: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113404

    We have ICE when we enable RVV in big-endian mode:

    during RTL pass: expand
    a-float-point-dynamic-frm-66.i:2:14: internal compiler error: in
to_constant, at poly-int.h:588
    0xab4c2c poly_int<2u, unsigned short>::to_constant() const
            /repo/gcc-trunk/gcc/poly-int.h:588
    0xab4de1 poly_int<2u, unsigned short>::to_constant() const
            /repo/gcc-trunk/gcc/tree.h:4055
    0xab4de1 default_function_arg_padding(machine_mode, tree_node const*)
            /repo/gcc-trunk/gcc/targhooks.cc:844
    0x12e2327 locate_and_pad_parm(machine_mode, tree_node*, int, int, int,
tree_node*, args_size*, locate_and_pad_arg_data*)
            /repo/gcc-trunk/gcc/function.cc:4061
    0x12e2aca assign_parm_find_entry_rtl
            /repo/gcc-trunk/gcc/function.cc:2614
    0x12e2c89 assign_parms
            /repo/gcc-trunk/gcc/function.cc:3693
    0x12e59df expand_function_start(tree_node*)
            /repo/gcc-trunk/gcc/function.cc:5152
    0x112fafb execute
            /repo/gcc-trunk/gcc/cfgexpand.cc:6739

    Report users that we don't support RVV in big-endian mode for the following
reasons:
    1. big-endian in RISC-V is pretty rare case.
    2. We didn't test RVV in big-endian and we don't have enough time to test
it since it's stage 4 now.

    Naive disallow RVV in big-endian.

    Tested no regression, ok for trunk ?

    gcc/ChangeLog:

            PR target/113404
            * config/riscv/riscv.cc (riscv_override_options_internal): Report
sorry
            for RVV in big-endian mode.

    gcc/testsuite/ChangeLog:

            PR target/113404
            * gcc.target/riscv/rvv/base/big_endian-1.c: New test.
            * gcc.target/riscv/rvv/base/big_endian-2.c: New test.

      reply	other threads:[~2024-01-16  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 18:24 [Bug target/113404] New: " zsojka at seznam dot cz
2024-01-16  3:20 ` cvs-commit at gcc dot gnu.org [this message]

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-113404-4-eyEmMmqVai@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).