[llvm-branch-commits] [clang] [RISCV] Integrate RISCV target in baremetal toolchain object and deprecate RISCVToolchain object (PR #121831)
Garvit Gupta via llvm-branch-commits
llvm-branch-commits at lists.llvm.org
Fri Apr 4 13:16:49 PDT 2025
================
@@ -336,6 +336,26 @@ BareMetal::OrderedMultilibs BareMetal::getOrderedMultilibs() const {
return llvm::reverse(Default);
}
+ToolChain::CXXStdlibType BareMetal::GetDefaultCXXStdlibType() const {
+ if (getTriple().isRISCV() && GCCInstallation.isValid())
+ return ToolChain::CST_Libstdcxx;
+ return ToolChain::CST_Libcxx;
+}
+
+ToolChain::RuntimeLibType BareMetal::GetDefaultRuntimeLibType() const {
+ if (getTriple().isRISCV() && GCCInstallation.isValid())
----------------
quic-garvgupt wrote:
This will modify the behavior for other targets. I understand that other targets can benefit from this as well however in this series of patches I will like to preserve the behavior as it was before merging RISCVToolchain into Baremetal toolchain object. If needed, I can push a separate PR (not a part of this series of patches) after merging of toolchain objects is done to ensure that other downstream toolchain vendors are not affected by this series of patches as it will already cause some churn in their code.
I will like to keep it as is until there is strong opinion to change the behavior in this patch itself
https://github.com/llvm/llvm-project/pull/121831
More information about the llvm-branch-commits
mailing list