From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
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: Thu, 17 Oct 2024 16:30:35 +0000 [thread overview]
Message-ID: <172918263598.2528145.14698302036420162335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241001-playlist-deceiving-16ece2f440f5@spud>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 1 Oct 2024 12:28:13 +0100 you 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, 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.
>
> [...]
Here is the summary with links:
- [v1] RISC-V: disallow gcc + rust builds
https://git.kernel.org/riscv/c/e52d5050a0d2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
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: Thu, 17 Oct 2024 16:30:35 +0000 [thread overview]
Message-ID: <172918263598.2528145.14698302036420162335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241001-playlist-deceiving-16ece2f440f5@spud>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 1 Oct 2024 12:28:13 +0100 you 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, 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.
>
> [...]
Here is the summary with links:
- [v1] RISC-V: disallow gcc + rust builds
https://git.kernel.org/riscv/c/e52d5050a0d2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-10-17 16:30 UTC|newest]
Thread overview: 20+ 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 11:28 ` Conor Dooley
2024-10-01 15:12 ` Miguel Ojeda
2024-10-01 15:12 ` Miguel Ojeda
2024-10-01 18:55 ` Nathan Chancellor
2024-10-01 18:55 ` Nathan Chancellor
2024-10-01 19:27 ` Conor Dooley
2024-10-01 19:27 ` Conor Dooley
2024-10-09 7:46 ` Alexandre Ghiti
2024-10-09 7:46 ` Alexandre Ghiti
2024-10-09 8:10 ` Alexandre Ghiti
2024-10-09 8:10 ` Alexandre Ghiti
2024-10-09 8:23 ` Conor Dooley
2024-10-09 8:23 ` Conor Dooley
2024-10-09 8:34 ` Alexandre Ghiti
2024-10-09 8:34 ` Alexandre Ghiti
2024-10-09 12:52 ` Miguel Ojeda
2024-10-09 12:52 ` Miguel Ojeda
2024-10-17 16:30 ` patchwork-bot+linux-riscv [this message]
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=172918263598.2528145.14698302036420162335.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--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 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.