From: Conor Dooley <conor@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>,
Nathan Chancellor <nathan@kernel.org>,
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, stable@vger.kernel.org
Subject: Re: [PATCH v2] riscv: Handle zicsr/zifencei issue between gcc and binutils
Date: Wed, 26 Jul 2023 20:41:55 +0100 [thread overview]
Message-ID: <20230726-armchair-evasive-427dd245a9fe@spud> (raw)
In-Reply-To: <10231b81-ea42-26d0-4c11-92851229e658@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Thu, Jul 27, 2023 at 03:34:16AM +0800, Mingzheng Xing wrote:
> On 7/27/23 02:02, Conor Dooley wrote:
> > This is still broken for:
> > CONFIG_CLANG_VERSION=0
> > CONFIG_AS_IS_GNU=y
> > CONFIG_AS_VERSION=23500
> > CONFIG_LD_IS_BFD=y
> > CONFIG_LD_VERSION=23500
>
> Do you mean that these CONFIG_* will cause kernel
> compilation errors when paired with certain versions of GCC?
> Or perhaps I misunderstood your meaning.
No, this section is generated by kconfig, although I messed up my
trimming of the list & accidentally removed the gcc version, rather
than the clang version. Here's the full thing:
CONFIG_CC_VERSION_TEXT="riscv64-unknown-linux-gnu-gcc (g2ee5e430018) 12.2.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=120200
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=23500
CONFIG_LD_IS_BFD=y
CONFIG_LD_VERSION=23500
CONFIG_LLD_VERSION=0
CONFIG_CC_CAN_LINK=y
CONFIG_CC_CAN_LINK_STATIC=y
CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y
CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y
CONFIG_PAHOLE_VERSION=0
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_TABLE_SORT=y
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-26 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 17:45 [PATCH v2] riscv: Handle zicsr/zifencei issue between gcc and binutils Mingzheng Xing
2023-07-26 17:49 ` kernel test robot
2023-07-26 18:02 ` Conor Dooley
2023-07-26 19:34 ` Mingzheng Xing
2023-07-26 19:41 ` Conor Dooley [this message]
2023-07-27 7:53 ` Conor Dooley
2023-07-29 17:36 ` Mingzheng Xing
2023-07-29 17:48 ` Conor Dooley
2023-07-31 10:16 ` Mingzheng Xing
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=20230726-armchair-evasive-427dd245a9fe@spud \
--to=conor@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=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.kernel.org \
--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: 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