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/102957] [riscv64] ICE on bogus -march value
Date: Mon, 28 Mar 2022 06:43:18 +0000	[thread overview]
Message-ID: <bug-102957-4-SeDEMrV6YK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102957-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Kito Cheng <kito@gcc.gnu.org>:

https://gcc.gnu.org/g:40e9979cf531e6a1ca1db8804c80e40e0e71de4c

commit r11-9700-g40e9979cf531e6a1ca1db8804c80e40e0e71de4c
Author: Kito Cheng <kito.cheng@sifive.com>
Date:   Mon Nov 8 22:45:49 2021 +0800

    [PR/target 102957] Allow Z*-ext extension with only 2 char.

    We was assume the Z* extension should be more than 2 char, so we put an
    assertion there, but it should just an error or warning rather than an
    assertion, however RISC-V has add `Zk` extension, which just 2 char, so
    actually, we should just allow that.

    gcc/ChangeLog

            PR target/102957
            * common/config/riscv/riscv-common.c (multi_letter_subset_rank):
Remove
            assertion for Z*-ext.

    gcc/testsuite/ChangeLog

            * gcc.target/riscv/pr102957.c: New.

    (cherry picked from commit abe562bb01479ea2c8952ad98714f3225527aa7e)

  parent reply	other threads:[~2022-03-28  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 21:42 [Bug driver/102957] New: " jengelh at inai dot de
2021-11-01 14:41 ` [Bug target/102957] " kito at gcc dot gnu.org
2021-11-09 16:26 ` cvs-commit at gcc dot gnu.org
2021-11-09 16:29 ` kito at gcc dot gnu.org
2022-03-28  6:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-28  6:43 ` kito at gcc dot gnu.org
2023-08-29 13:49 ` cvs-commit 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-102957-4-SeDEMrV6YK@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).