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/111362] [14 Regression] '-fcompare-debug' failure (length) with -O -fno-tree-ch --param=max-completely-peel-times=0 -march=rv64iv
Date: Wed, 13 Sep 2023 06:19:37 +0000	[thread overview]
Message-ID: <bug-111362-4-LK51ZlYkQJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111362-4@http.gcc.gnu.org/bugzilla/>

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

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

commit r14-3915-gfeb23a37e6142016c3463aa3be3e900d45bc3ea5
Author: Pan Li <pan2.li@intel.com>
Date:   Wed Sep 13 11:34:42 2023 +0800

    RISC-V: Bugfix PR111362 for incorrect frm emit

    When the mode switching from NONE to CALL, we will restore the
    frm but lack some check if we have static frm insn in cfun.

    This patch would like to fix this by adding static frm insn check.

            PR target/111362

    gcc/ChangeLog:

            * config/riscv/riscv.cc (riscv_emit_frm_mode_set): Bugfix.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/base/no-honor-frm-1.c: New test.

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

  parent reply	other threads:[~2023-09-13  6:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 11:15 [Bug target/111362] New: " zsojka at seznam dot cz
2023-09-12 12:20 ` [Bug target/111362] " rguenth at gcc dot gnu.org
2023-09-13  6:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-14 15:10 ` zsojka at seznam dot cz
2024-03-09 17:46 ` law at gcc dot gnu.org
2024-03-09 23:45 ` law at gcc dot gnu.org
2024-03-10  2:39 ` cvs-commit at gcc dot gnu.org
2024-03-10  2:40 ` 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-111362-4-LK51ZlYkQJ@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).