public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: gcc-patches@gcc.gnu.org, Palmer Dabbelt <palmer@rivosinc.com>,
	 Christoph Muellner <christoph.muellner@vrull.eu>,
	Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [PATCH] RISC-V: Fix selection of pipeline model for sifive-7-series
Date: Wed, 9 Nov 2022 17:03:08 -0800	[thread overview]
Message-ID: <CA+yXCZAtoXrOfx7amuVjEtc+PWB_C0MpMhM=P+FQ8GNEzvfd5Q@mail.gmail.com> (raw)
In-Reply-To: <20221109234948.3279391-1-philipp.tomsich@vrull.eu>

LGTM, thank you for catching that!!

On Wed, Nov 9, 2022 at 3:50 PM Philipp Tomsich <philipp.tomsich@vrull.eu> wrote:
>
> A few of the gcc.target/riscv/mcpu-*.c tests have been failing for a
> while now, due to the pipeline model for sifive-7-series not being
> selected despite -mtune=sifive-7-series.  The root cause is that the
> respective RISCV_TUNE entry points to generic instead.  Fix this.
>
> Fixes 97d1ed67fc6 ("RISC-V: Support --target-help for -mcpu/-mtune")
>
> gcc/ChangeLog:
>
>         * config/riscv/riscv-cores.def (RISCV_TUNE): Update
>           sifive-7-series to point to the sifive_7 pipeline
>           description.
>
> Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
> ---
>
>  gcc/config/riscv/riscv-cores.def | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/config/riscv/riscv-cores.def b/gcc/config/riscv/riscv-cores.def
> index b84ad999ac1..31ad34682c5 100644
> --- a/gcc/config/riscv/riscv-cores.def
> +++ b/gcc/config/riscv/riscv-cores.def
> @@ -36,7 +36,7 @@
>  RISCV_TUNE("rocket", generic, rocket_tune_info)
>  RISCV_TUNE("sifive-3-series", generic, rocket_tune_info)
>  RISCV_TUNE("sifive-5-series", generic, rocket_tune_info)
> -RISCV_TUNE("sifive-7-series", generic, sifive_7_tune_info)
> +RISCV_TUNE("sifive-7-series", sifive_7, sifive_7_tune_info)
>  RISCV_TUNE("thead-c906", generic, thead_c906_tune_info)
>  RISCV_TUNE("size", generic, optimize_size_tune_info)
>
> --
> 2.34.1
>

  reply	other threads:[~2022-11-10  1:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 23:49 Philipp Tomsich
2022-11-10  1:03 ` Kito Cheng [this message]
2022-11-10 13:58   ` Philipp Tomsich

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='CA+yXCZAtoXrOfx7amuVjEtc+PWB_C0MpMhM=P+FQ8GNEzvfd5Q@mail.gmail.com' \
    --to=kito.cheng@gmail.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=palmer@rivosinc.com \
    --cc=philipp.tomsich@vrull.eu \
    /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).