From: Nathan Chancellor <nathan@kernel.org> To: Mingzheng Xing <xingmingzheng@iscas.ac.cn> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Nick Desaulniers <ndesaulniers@google.com>, Tom Rix <trix@redhat.com>, Bin Meng <bmeng@tinylab.org>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev Subject: Re: [PATCH] riscv: Handle zicsr/zifencei issue between gcc and binutils Date: Tue, 25 Jul 2023 10:23:44 -0700 [thread overview] Message-ID: <20230725172344.GA1445373@dev-arch.thelio-3990X> (raw) In-Reply-To: <20230725170405.251011-1-xingmingzheng@iscas.ac.cn> Hi Mingzheng, Thanks for the patch! On Wed, Jul 26, 2023 at 01:04:05AM +0800, Mingzheng Xing wrote: > When compiling the kernel with the toolchain composed of GCC >= 12.1.0 and > binutils < 2.38, default ISA spec used when building binutils and GCC, the > following build failure will appear because the > CONFIG_TOOLCHAIN_NEEDS_EXPLICIT_ZICSR_ZIFENCEI is not turned on. > (i.e, gcc-12.1.0 and binutils-2.36, or gcc-12.3.0 and binutils-2.37, use > default ISA spec.) > > CC arch/riscv/kernel/vdso/vgettimeofday.o > <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h: Assembler messages: > <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:79: Error: unrecognized opcode `csrr a5,0xc01' The gift that keeps on giving :/ > Binutils has updated the default ISA spec version, and the community has > responded well to this[1][2][3], but it appears that this is not over yet. > > We also need to consider the situation of binutils < 2.38 but > GCC >= 12.1.0, since the combination between different versions of GCC and > binutils is not unique, which is to some extent flexible. GCC release > 12.1.0 updated the default ISA spec version in GCC commit[4]. I suspect this combination is not too common because binutils 2.38 came out before GCC 12.1.0 but as you note, it is obviously possible. What toolchain has this combination in the wild, which would be helpful for documentation purposes? > For more information, please refer to: > > commit 6df2a016c0c8 ("riscv: fix build with binutils 2.38") > commit e89c2e815e76 ("riscv: Handle zicsr/zifencei issues between clang and binutils") > > [1]: https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/aE1ZeHHCYf4 > [2]: https://lore.kernel.org/all/20230308220842.1231003-1-conor@kernel.org > [3]: https://lore.kernel.org/all/20230223220546.52879-1-conor@kernel.org > [4]: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=98416dbb0a62579d4a7a4a76bab51b5b52fec2cd > > Signed-off-by: Mingzheng Xing <xingmingzheng@iscas.ac.cn> > --- > arch/riscv/Kconfig | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index 4c07b9189c86..b49cea30f6cc 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -570,11 +570,15 @@ config TOOLCHAIN_HAS_ZIHINTPAUSE > config TOOLCHAIN_NEEDS_EXPLICIT_ZICSR_ZIFENCEI > def_bool y > # https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=aed44286efa8ae8717a77d94b51ac3614e2ca6dc > - depends on AS_IS_GNU && AS_VERSION >= 23800 > + # https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=98416dbb0a62579d4a7a4a76bab51b5b52fec2cd > + depends on CC_IS_GCC && GCC_VERSION >= 120100 || \ > + AS_IS_GNU && AS_VERSION >= 23800 GCC_VERSION will be 0 for clang, so you don't need the CC_IS_GCC check. With that change, this should be able to stay on one line: depends on GCC_VERSION >= 120100 || (AS_IS_GNU && AS_VERSION >= 23800) > help > Newer binutils versions default to ISA spec version 20191213 which > moves some instructions from the I extension to the Zicsr and Zifencei > extensions. > + Similarly, GCC release 12.1.0 has changed the default ISA spec version to > + 20191213, so the above situation requires this option to be enabled. > > config TOOLCHAIN_NEEDS_OLD_ISA_SPEC > def_bool y > -- > 2.34.1 > Cheers, Nathan
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org> To: Mingzheng Xing <xingmingzheng@iscas.ac.cn> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Nick Desaulniers <ndesaulniers@google.com>, Tom Rix <trix@redhat.com>, Bin Meng <bmeng@tinylab.org>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev Subject: Re: [PATCH] riscv: Handle zicsr/zifencei issue between gcc and binutils Date: Tue, 25 Jul 2023 10:23:44 -0700 [thread overview] Message-ID: <20230725172344.GA1445373@dev-arch.thelio-3990X> (raw) In-Reply-To: <20230725170405.251011-1-xingmingzheng@iscas.ac.cn> Hi Mingzheng, Thanks for the patch! On Wed, Jul 26, 2023 at 01:04:05AM +0800, Mingzheng Xing wrote: > When compiling the kernel with the toolchain composed of GCC >= 12.1.0 and > binutils < 2.38, default ISA spec used when building binutils and GCC, the > following build failure will appear because the > CONFIG_TOOLCHAIN_NEEDS_EXPLICIT_ZICSR_ZIFENCEI is not turned on. > (i.e, gcc-12.1.0 and binutils-2.36, or gcc-12.3.0 and binutils-2.37, use > default ISA spec.) > > CC arch/riscv/kernel/vdso/vgettimeofday.o > <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h: Assembler messages: > <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:79: Error: unrecognized opcode `csrr a5,0xc01' The gift that keeps on giving :/ > Binutils has updated the default ISA spec version, and the community has > responded well to this[1][2][3], but it appears that this is not over yet. > > We also need to consider the situation of binutils < 2.38 but > GCC >= 12.1.0, since the combination between different versions of GCC and > binutils is not unique, which is to some extent flexible. GCC release > 12.1.0 updated the default ISA spec version in GCC commit[4]. I suspect this combination is not too common because binutils 2.38 came out before GCC 12.1.0 but as you note, it is obviously possible. What toolchain has this combination in the wild, which would be helpful for documentation purposes? > For more information, please refer to: > > commit 6df2a016c0c8 ("riscv: fix build with binutils 2.38") > commit e89c2e815e76 ("riscv: Handle zicsr/zifencei issues between clang and binutils") > > [1]: https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/aE1ZeHHCYf4 > [2]: https://lore.kernel.org/all/20230308220842.1231003-1-conor@kernel.org > [3]: https://lore.kernel.org/all/20230223220546.52879-1-conor@kernel.org > [4]: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=98416dbb0a62579d4a7a4a76bab51b5b52fec2cd > > Signed-off-by: Mingzheng Xing <xingmingzheng@iscas.ac.cn> > --- > arch/riscv/Kconfig | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index 4c07b9189c86..b49cea30f6cc 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -570,11 +570,15 @@ config TOOLCHAIN_HAS_ZIHINTPAUSE > config TOOLCHAIN_NEEDS_EXPLICIT_ZICSR_ZIFENCEI > def_bool y > # https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=aed44286efa8ae8717a77d94b51ac3614e2ca6dc > - depends on AS_IS_GNU && AS_VERSION >= 23800 > + # https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=98416dbb0a62579d4a7a4a76bab51b5b52fec2cd > + depends on CC_IS_GCC && GCC_VERSION >= 120100 || \ > + AS_IS_GNU && AS_VERSION >= 23800 GCC_VERSION will be 0 for clang, so you don't need the CC_IS_GCC check. With that change, this should be able to stay on one line: depends on GCC_VERSION >= 120100 || (AS_IS_GNU && AS_VERSION >= 23800) > help > Newer binutils versions default to ISA spec version 20191213 which > moves some instructions from the I extension to the Zicsr and Zifencei > extensions. > + Similarly, GCC release 12.1.0 has changed the default ISA spec version to > + 20191213, so the above situation requires this option to be enabled. > > config TOOLCHAIN_NEEDS_OLD_ISA_SPEC > def_bool y > -- > 2.34.1 > Cheers, Nathan _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-25 17:23 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-25 17:04 [PATCH] riscv: Handle zicsr/zifencei issue between gcc and binutils Mingzheng Xing 2023-07-25 17:04 ` Mingzheng Xing 2023-07-25 17:23 ` Nathan Chancellor [this message] 2023-07-25 17:23 ` Nathan Chancellor 2023-07-25 18:57 ` Conor Dooley 2023-07-25 18:57 ` Conor Dooley 2023-07-25 22:17 ` Conor Dooley 2023-07-25 22:17 ` Conor Dooley 2023-07-26 16:55 ` Mingzheng Xing 2023-07-26 16:55 ` Mingzheng Xing 2023-07-26 16:53 ` Mingzheng Xing 2023-07-26 16:53 ` Mingzheng Xing 2023-07-26 16:48 ` Mingzheng Xing 2023-07-26 16:48 ` Mingzheng Xing [not found] <20230731095534.22842-1-xingmingzheng@iscas.ac.cn> 2023-07-31 15:05 ` Mingzheng Xing 2023-07-31 15:05 ` Mingzheng Xing 2023-07-31 15:24 ` Conor Dooley 2023-07-31 15:24 ` Conor Dooley 2023-07-31 15:50 ` Mingzheng Xing 2023-07-31 15:50 ` Mingzheng Xing 2023-08-01 10:59 ` Guo Ren 2023-08-01 10:59 ` Guo Ren
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=20230725172344.GA1445373@dev-arch.thelio-3990X \ --to=nathan@kernel.org \ --cc=aou@eecs.berkeley.edu \ --cc=bmeng@tinylab.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=ndesaulniers@google.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=trix@redhat.com \ --cc=xingmingzheng@iscas.ac.cn \ /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.