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/111546] [14 Regression] ICE: gfortran.dg/overload_5.f90:53:2: internal compiler error: in emit_move_insn, at expr.cc:4219 since r14-4163-gbea89f78f2f
Date: Sun, 24 Sep 2023 09:10:09 +0000	[thread overview]
Message-ID: <bug-111546-4-Re5I4aoBff@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111546-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS 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:deb844c67f1e2b116518f9742a6acbe6f19ea28f

commit r14-4243-gdeb844c67f1e2b116518f9742a6acbe6f19ea28f
Author: Pan Li <pan2.li@intel.com>
Date:   Sun Sep 24 11:36:11 2023 +0800

    RISC-V: Fix fortran ICE/PR111546 when RV32 vec_init

    When broadcast the reperated element, we take the mask_int_mode
    by mistake. This patch would like to fix it by leveraging the machine
    mode of the element.

    The below test case in RV32 will be fixed.

    * gcc/testsuite/gfortran.dg/overload_5.f90

            PR target/111546

    gcc/ChangeLog:

            * config/riscv/riscv-v.cc
            (expand_vector_init_merge_repeating_sequence): Bugfix

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

  parent reply	other threads:[~2023-09-24  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 23:25 [Bug target/111546] New: " patrick at rivosinc dot com
2023-09-22 23:27 ` [Bug target/111546] " patrick at rivosinc dot com
2023-09-23  6:31 ` rguenth at gcc dot gnu.org
2023-09-24  9:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-25 15:55 ` patrick at rivosinc dot com

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-111546-4-Re5I4aoBff@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).