From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jamie Gibbons via buildroot <buildroot@buildroot.org>
Cc: Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Conor Dooley <Conor.Dooley@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: Re: [Buildroot] [PATCH 1/3] arch/Config.in.riscv: update instruction set ext
Date: Tue, 15 Aug 2023 21:38:16 +0200 [thread overview]
Message-ID: <20230815213816.38960e1e@windsurf> (raw)
In-Reply-To: <20230815100600.297932-2-jamie.gibbons@microchip.com>
On Tue, 15 Aug 2023 11:05:58 +0100
Jamie Gibbons via buildroot <buildroot@buildroot.org> wrote:
> +if BR2_riscv_g
> +
> +comment "Instruction Set Extensions"
> +
> +config BR2_RISCV_ISA_CUSTOM_RVC
> + bool "Compressed Instructions (C)"
> + select BR2_RISCV_ISA_RVC
> +
> +config BR2_RISCV_ISA_CUSTOM_RVV
> + bool "Vector Instructions (V)"
> + select BR2_RISCV_ISA_RVV
> + select BR2_ARCH_NEEDS_GCC_AT_LEAST_12
> +
> +endif
I believe this is still not correct: now those options are only
available for the BR2_riscv_g case, no longer for the custom RISC-V
core case.
Those two options should be available both as add-ons for the riscv_g
*and* for the riscv custom cases.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-15 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 10:05 [Buildroot] [PATCH 0/3] Update RISC-V Instruction Sets Jamie Gibbons via buildroot
2023-08-15 10:05 ` [Buildroot] [PATCH 1/3] arch/Config.in.riscv: update instruction set ext Jamie Gibbons via buildroot
2023-08-15 19:38 ` Thomas Petazzoni via buildroot [this message]
2023-08-16 7:19 ` Jamie.Gibbons--- via buildroot
2023-08-15 10:05 ` [Buildroot] [PATCH 2/3] configs/microchip_mpfs_icicle_defconfig: update instruction sets Jamie Gibbons via buildroot
2023-08-15 10:06 ` [Buildroot] [PATCH 3/3] board/microchip/mpfs_icicle: update post-image script Jamie Gibbons via buildroot
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=20230815213816.38960e1e@windsurf \
--to=buildroot@buildroot.org \
--cc=Conor.Dooley@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=jamie.gibbons@microchip.com \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.