================
@@ -1462,10 +1462,12 @@ WindowsARM64TargetInfo::WindowsARM64TargetInfo(const
llvm::Triple &Triple,
}
void WindowsARM64TargetInfo::setDataLayout() {
- resetDataLayout(Triple.isOSBinFormatMachO()
- ? "e-m:o-i64:64-i128:128-n32:64-S128"
- : "e-m:w-p:64:64-i32:32-i64:64-i128:128-n32:64-S128",
- Triple.isOSBinFormatMachO() ? "_" : "");
+ if (Triple.isOSBinFormatMachO()) {
+ resetDataLayout("e-m:o-i64:64-i128:128-n32:64-S128", "_");
----------------
mstorsjo wrote:
AFAIK Windows+MachO is used in some cases for JIT scenarios, because the
runtime linking support in the JIT is much more complete for MachO than it is
for PE/COFF.
https://github.com/llvm/llvm-project/pull/78913
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
