From: Alexandre Ghiti <alex@ghiti.fr>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Jason Montleon <jmontleo@redhat.com>,
ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v1] RISC-V: disallow gcc + rust builds
Date: Wed, 9 Oct 2024 10:10:14 +0200 [thread overview]
Message-ID: <c4906bfc-5bc1-428e-a76f-3fb0bb8711ac@ghiti.fr> (raw)
In-Reply-To: <250e1e5d-5110-414f-abbd-fb002e715f32@ghiti.fr>
On 09/10/2024 09:46, Alexandre Ghiti wrote:
> Hi Conor,
>
> On 01/10/2024 13:28, Conor Dooley wrote:
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> During the discussion before supporting rust on riscv, it was decided
>> not to support gcc yet, due to differences in extension handling
>> compared to llvm (only the version of libclang matching the c compiler
>> is supported). Recently Jason Montleon reported [1] that building with
>> gcc caused build issues, due to unsupported arguments being passed to
>> libclang. After some discussion between myself and Miguel
>
>
> I have just added "[2]" here as it seemed to be missing.
>
> Thanks,
>
> Alex
>
>
>> , it is better
>> to disable gcc + rust builds to match the original intent, and
>> subsequently support it when an appropriate set of extensions can be
>> deduced from the version of libclang.
>>
>> Closes:
>> https://lore.kernel.org/all/20240917000848.720765-2-jmontleo@redhat.com/
>> [1]
>> Link:
>> https://lore.kernel.org/all/20240926-battering-revolt-6c6a7827413e@spud/
>> [2]
>> Fixes: 70a57b247251a ("RISC-V: enable building 64-bit kernels with
>> rust support")
I also fixed the Fixes tag ^, it contains 13 characters instead of 12
and added a cc: stable tag.
>> Reported-by: Jason Montleon <jmontleo@redhat.com>
And I moved this tag above the Closes tag.
Thanks,
Alex
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>>
>> Palmer, this is yours to take.
>>
>> CC: jmontleo@redhat.com
>> CC: ojeda@kernel.org
>> CC: alex.gaynor@gmail.com
>> CC: boqun.feng@gmail.com
>> CC: gary@garyguo.net
>> CC: bjorn3_gh@protonmail.com
>> CC: benno.lossin@proton.me
>> CC: a.hindborg@kernel.org
>> CC: aliceryhl@google.com
>> CC: paul.walmsley@sifive.com
>> CC: palmer@dabbelt.com
>> CC: nathan@kernel.org
>> CC: ndesaulniers@google.com
>> CC: morbo@google.com
>> CC: justinstitt@google.com
>> CC: rust-for-linux@vger.kernel.org
>> CC: linux-riscv@lists.infradead.org
>> CC: llvm@lists.linux.dev
>> ---
>> Documentation/rust/arch-support.rst | 2 +-
>> arch/riscv/Kconfig | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/rust/arch-support.rst
>> b/Documentation/rust/arch-support.rst
>> index 750ff371570a0..54be7ddf3e57a 100644
>> --- a/Documentation/rust/arch-support.rst
>> +++ b/Documentation/rust/arch-support.rst
>> @@ -17,7 +17,7 @@ Architecture Level of support Constraints
>> ============= ================
>> ==============================================
>> ``arm64`` Maintained Little Endian only.
>> ``loongarch`` Maintained \-
>> -``riscv`` Maintained ``riscv64`` only.
>> +``riscv`` Maintained ``riscv64`` and LLVM/Clang only.
>> ``um`` Maintained \-
>> ``x86`` Maintained ``x86_64`` only.
>> ============= ================
>> ==============================================
>> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>> index 22dc5ea4196ce..76843584960c2 100644
>> --- a/arch/riscv/Kconfig
>> +++ b/arch/riscv/Kconfig
>> @@ -177,7 +177,7 @@ config RISCV
>> select HAVE_REGS_AND_STACK_ACCESS_API
>> select HAVE_RETHOOK if !XIP_KERNEL
>> select HAVE_RSEQ
>> - select HAVE_RUST if RUSTC_SUPPORTS_RISCV
>> + select HAVE_RUST if RUSTC_SUPPORTS_RISCV && CC_IS_CLANG
>> select HAVE_SAMPLE_FTRACE_DIRECT
>> select HAVE_SAMPLE_FTRACE_DIRECT_MULTI
>> select HAVE_STACKPROTECTOR
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-10-09 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:28 [PATCH v1] RISC-V: disallow gcc + rust builds Conor Dooley
2024-10-01 15:12 ` Miguel Ojeda
2024-10-01 18:55 ` Nathan Chancellor
2024-10-01 19:27 ` Conor Dooley
2024-10-09 7:46 ` Alexandre Ghiti
2024-10-09 8:10 ` Alexandre Ghiti [this message]
2024-10-09 8:23 ` Conor Dooley
2024-10-09 8:34 ` Alexandre Ghiti
2024-10-09 12:52 ` Miguel Ojeda
2024-10-17 16:30 ` patchwork-bot+linux-riscv
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=c4906bfc-5bc1-428e-a76f-3fb0bb8711ac@ghiti.fr \
--to=alex@ghiti.fr \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=gary@garyguo.net \
--cc=jmontleo@redhat.com \
--cc=justinstitt@google.com \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rust-for-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).