Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
	Mark Corbin <mark@dibsco.co.uk>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH for-next 01/11] arch/Config.in.riscv: add Zicsr and Zifencei standalone extensions
Date: Sat, 23 Jul 2022 15:25:03 +0200	[thread overview]
Message-ID: <20220723152503.5e2417cb@windsurf> (raw)
In-Reply-To: <5fd9249b-0815-0b8a-9cb5-a301d04ec5d3@smile.fr>

Hello,

On Sat, 23 Jul 2022 15:00:40 +0200
Romain Naour <romain.naour@smile.fr> wrote:

> I'm not familiar with the riscv instruction set, so I was not sure if we should
> support the possibility to disable Zicsr and Zifencei standalone extensions with
> gcc 12. AFIU, they are unconditionally enabled in previous gcc releases.

Correct, which is why I think they will always be present in
Linux-capable RISC-V cores. The reason I believe they were split from
the I part of the ISA is because I is the base part of the ISA, and
some people wanted to make RISC-V designs without those instructions,
but not RISC-V designs targeting Linux.

So for now, I think we should simply make the assumption that all
RISC-V cores will have those instructions.

If that turns out to be wrong in the future, we can always revisit that.

> Additionally we have received two patches to add "vector operations extension"
> 
> http://patchwork.ozlabs.org/project/buildroot/patch/20220704085552.3499243-2-abel@x-silicon.com/
> 
> http://patchwork.ozlabs.org/project/buildroot/patch/20220627135359.2232222-1-fhunleth@troodon-software.com/
> 
> But this requires gcc-12
> 
> http://patchwork.ozlabs.org/project/buildroot/patch/20220627135359.2232222-1-fhunleth@troodon-software.com/#2933736
> 
> Do you think "Vector Instructions (V)" deserve an option ? (I would say yes).

Yes, V definitely needs an option, as there will clearly be
Linux-capable RISC-V cores that do not implement the V extension.

The option for the V extension will have to select
BR2_ARCH_NEEDS_GCC_AT_LEAST_12.

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

      reply	other threads:[~2022-07-23 13:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 13:18 [Buildroot] [PATCH for-next 01/11] arch/Config.in.riscv: add Zicsr and Zifencei standalone extensions Romain Naour
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 02/11] configs/qemu_riscv{32, 64}_virt: kernel bump version to 5.15.43 Romain Naour
2022-07-23 12:57   ` Thomas Petazzoni via buildroot
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 03/11] package/gcc: disable libsanitizer for mips64{el} w/ n32 ABI Romain Naour
2022-07-23 12:41   ` Thomas Petazzoni via buildroot
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 04/11] package/gcc: disable libsanitizer for mips{el} and gcc > 12 Romain Naour
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 05/11] toolchain: enable libquadmath for PowerPC with VSX Romain Naour
2022-07-23 12:57   ` Thomas Petazzoni via buildroot
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 06/11] package/gcc: add missing --enable-libquadmath-support option Romain Naour
2022-07-23 12:57   ` Thomas Petazzoni via buildroot
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 07/11] package/gcc: switch to https urls for archives hashes Romain Naour
2022-07-23 12:57   ` Thomas Petazzoni via buildroot
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 08/11] package/gcc: add support for gcc 12 Romain Naour
2022-06-25  6:45   ` James Hilliard
2022-07-16 11:31     ` Romain Naour
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 09/11] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_12 Romain Naour
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 10/11] package/gcc: switch to gcc 11.x as the default Romain Naour
2022-05-29 13:18 ` [Buildroot] [PATCH for-next 11/11] package/gcc: remove gcc 9.x Romain Naour
2022-07-23 12:39 ` [Buildroot] [PATCH for-next 01/11] arch/Config.in.riscv: add Zicsr and Zifencei standalone extensions Thomas Petazzoni via buildroot
2022-07-23 13:00   ` Romain Naour
2022-07-23 13:25     ` Thomas Petazzoni via buildroot [this message]

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=20220723152503.5e2417cb@windsurf \
    --to=buildroot@buildroot.org \
    --cc=mark@dibsco.co.uk \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox