From: Nathan Chancellor <nathan@kernel.org> To: Conor Dooley <conor@kernel.org> Cc: palmer@dabbelt.com, Conor Dooley <conor.dooley@microchip.com>, naresh.kamboju@linaro.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [PATCH v1 1/2] RISC-V: move zicsr/zifencei spec version check to Kconfig Date: Fri, 24 Feb 2023 09:37:28 -0700 [thread overview] Message-ID: <Y/jnyJZNZC1X6IO8@dev-arch.thelio-3990X> (raw) In-Reply-To: <20230223220546.52879-2-conor@kernel.org> On Thu, Feb 23, 2023 at 10:05:45PM +0000, Conor Dooley wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > Checking whether binutils defaults to using a version of the spec > requiring zicsr/zifencei being done in our Makefile is functionally > sufficient at present, but makes it harder to tell after the fact > which extensions are enabled. > By moving it to Kconfig, it's easy to tell from standard build artifacts > what has been done & the road is paved for dealing with this differently > for both binutils and LLVM. > > Signed-off-by: Conor Dooley <conor.dooley@microchip.com> Reviewed-by: Nathan Chancellor <nathan@kernel.org> > --- > arch/riscv/Kconfig | 10 ++++++++++ > arch/riscv/Makefile | 5 +---- > 2 files changed, 11 insertions(+), 4 deletions(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index cebf0c5f8824..4eb0ef8314b3 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -288,6 +288,16 @@ config ARCH_RV64I > > endchoice > > +config TOOLCHAIN_NEEDS_SPEC_20191213 This symbol's name is a little confusing to me, how does the toolchain need spec version 20191213. Maybe 'SPEC_20191213' should be something like 'EXPLICIT_ZICSR_ZIFENCEI'? Otherwise, maybe it should be something like 'TOOLCHAIN_HAS_DEFAULT_SPEC_20191213'? Sorry for the bikeshed but I think most Kconfig symbols should be self describing. > + bool > + default y > + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicsr_zifencei) > + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicsr_zifencei) > + help > + Newer binutils versions default to ISA spec version 20191213 which > + moves some instructions from the I extension to the Zicsr and Zifencei > + extensions. > + > # We must be able to map all physical memory into the kernel, but the compiler > # is still a bit more efficient when generating code if it's setup in a manner > # such that it can only map 2GiB of memory. > diff --git a/arch/riscv/Makefile b/arch/riscv/Makefile > index 12d91b0a73d8..7e1267b0e73f 100644 > --- a/arch/riscv/Makefile > +++ b/arch/riscv/Makefile > @@ -53,10 +53,7 @@ riscv-march-$(CONFIG_ARCH_RV64I) := rv64ima > riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd > riscv-march-$(CONFIG_RISCV_ISA_C) := $(riscv-march-y)c > > -# Newer binutils versions default to ISA spec version 20191213 which moves some > -# instructions from the I extension to the Zicsr and Zifencei extensions. > -toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) > -riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei > +riscv-march-$(CONFIG_TOOLCHAIN_NEEDS_SPEC_20191213) := $(riscv-march-y)_zicsr_zifencei > > # Check if the toolchain supports Zicbom extension > riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom > -- > 2.39.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org> To: Conor Dooley <conor@kernel.org> Cc: palmer@dabbelt.com, Conor Dooley <conor.dooley@microchip.com>, naresh.kamboju@linaro.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [PATCH v1 1/2] RISC-V: move zicsr/zifencei spec version check to Kconfig Date: Fri, 24 Feb 2023 09:37:28 -0700 [thread overview] Message-ID: <Y/jnyJZNZC1X6IO8@dev-arch.thelio-3990X> (raw) In-Reply-To: <20230223220546.52879-2-conor@kernel.org> On Thu, Feb 23, 2023 at 10:05:45PM +0000, Conor Dooley wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > Checking whether binutils defaults to using a version of the spec > requiring zicsr/zifencei being done in our Makefile is functionally > sufficient at present, but makes it harder to tell after the fact > which extensions are enabled. > By moving it to Kconfig, it's easy to tell from standard build artifacts > what has been done & the road is paved for dealing with this differently > for both binutils and LLVM. > > Signed-off-by: Conor Dooley <conor.dooley@microchip.com> Reviewed-by: Nathan Chancellor <nathan@kernel.org> > --- > arch/riscv/Kconfig | 10 ++++++++++ > arch/riscv/Makefile | 5 +---- > 2 files changed, 11 insertions(+), 4 deletions(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index cebf0c5f8824..4eb0ef8314b3 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -288,6 +288,16 @@ config ARCH_RV64I > > endchoice > > +config TOOLCHAIN_NEEDS_SPEC_20191213 This symbol's name is a little confusing to me, how does the toolchain need spec version 20191213. Maybe 'SPEC_20191213' should be something like 'EXPLICIT_ZICSR_ZIFENCEI'? Otherwise, maybe it should be something like 'TOOLCHAIN_HAS_DEFAULT_SPEC_20191213'? Sorry for the bikeshed but I think most Kconfig symbols should be self describing. > + bool > + default y > + depends on !64BIT || $(cc-option,-mabi=lp64 -march=rv64ima_zicsr_zifencei) > + depends on !32BIT || $(cc-option,-mabi=ilp32 -march=rv32ima_zicsr_zifencei) > + help > + Newer binutils versions default to ISA spec version 20191213 which > + moves some instructions from the I extension to the Zicsr and Zifencei > + extensions. > + > # We must be able to map all physical memory into the kernel, but the compiler > # is still a bit more efficient when generating code if it's setup in a manner > # such that it can only map 2GiB of memory. > diff --git a/arch/riscv/Makefile b/arch/riscv/Makefile > index 12d91b0a73d8..7e1267b0e73f 100644 > --- a/arch/riscv/Makefile > +++ b/arch/riscv/Makefile > @@ -53,10 +53,7 @@ riscv-march-$(CONFIG_ARCH_RV64I) := rv64ima > riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd > riscv-march-$(CONFIG_RISCV_ISA_C) := $(riscv-march-y)c > > -# Newer binutils versions default to ISA spec version 20191213 which moves some > -# instructions from the I extension to the Zicsr and Zifencei extensions. > -toolchain-need-zicsr-zifencei := $(call cc-option-yn, -march=$(riscv-march-y)_zicsr_zifencei) > -riscv-march-$(toolchain-need-zicsr-zifencei) := $(riscv-march-y)_zicsr_zifencei > +riscv-march-$(CONFIG_TOOLCHAIN_NEEDS_SPEC_20191213) := $(riscv-march-y)_zicsr_zifencei > > # Check if the toolchain supports Zicbom extension > riscv-march-$(CONFIG_TOOLCHAIN_HAS_ZICBOM) := $(riscv-march-y)_zicbom > -- > 2.39.1 > _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-02-24 16:37 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-23 22:05 [PATCH v1 0/2] RISC-V: avoid build issues for clang/llvm-17 with binutils 2.35 Conor Dooley 2023-02-23 22:05 ` Conor Dooley 2023-02-23 22:05 ` [PATCH v1 1/2] RISC-V: move zicsr/zifencei spec version check to Kconfig Conor Dooley 2023-02-23 22:05 ` Conor Dooley 2023-02-24 16:37 ` Nathan Chancellor [this message] 2023-02-24 16:37 ` Nathan Chancellor 2023-02-24 17:00 ` Conor Dooley 2023-02-24 17:00 ` Conor Dooley 2023-03-06 23:52 ` Palmer Dabbelt 2023-03-06 23:52 ` Palmer Dabbelt 2023-03-07 19:14 ` Conor Dooley 2023-03-07 19:14 ` Conor Dooley 2023-03-07 19:24 ` Palmer Dabbelt 2023-03-07 19:24 ` Palmer Dabbelt 2023-02-23 22:05 ` [PATCH v1 2/2] RISC-V: make TOOLCHAIN_NEEDS_SPEC_20191213 gas only Conor Dooley 2023-02-23 22:05 ` Conor Dooley 2023-02-24 16:32 ` Nathan Chancellor 2023-02-24 16:32 ` Nathan Chancellor
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=Y/jnyJZNZC1X6IO8@dev-arch.thelio-3990X \ --to=nathan@kernel.org \ --cc=conor.dooley@microchip.com \ --cc=conor@kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=naresh.kamboju@linaro.org \ --cc=palmer@dabbelt.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: linkBe 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.