arjunr2 wrote:
Ping
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -199,6 +199,7 @@ class Triple {
SUSE,
OpenEmbedded,
Intel,
+WALI,
arjunr2 wrote:
We're really not adding a new OS to the set of triples here since we're reusing
Linux, just the new ABI for Wasm.
It's not too late to modify the rustc, but n
https://github.com/arjunr2 edited
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
arjunr2 wrote:
Created an
[RFC](https://discourse.llvm.org/t/rfc-new-wasm-linux-target-support/88203)
detailing the discussion
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm
https://github.com/arjunr2 updated
https://github.com/llvm/llvm-project/pull/156087
>From cb996a12aa20c65980f620381731fad1622e0417 Mon Sep 17 00:00:00 2001
From: Arjun Ramesh
Date: Sat, 30 Aug 2025 01:01:02 -0400
Subject: [PATCH 1/4] Support for `wasm32-wali-linux-musl target` in `clang`,
`lld
https://github.com/arjunr2 edited
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -199,6 +199,7 @@ class Triple {
SUSE,
OpenEmbedded,
Intel,
+WALI,
arjunr2 wrote:
@aheejin `cfg` is how feature gating based on targets is performed at Rust.
This is fully independent of the LLVM target backend, so we can make the host
envi
@@ -199,6 +199,7 @@ class Triple {
SUSE,
OpenEmbedded,
Intel,
+WALI,
arjunr2 wrote:
I think for consistency it makes sense to have it described as a vendor here as
well. It should be a simple to update the target later if necessary.
https://g
https://github.com/arjunr2 edited
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/arjunr2 edited
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/arjunr2 edited
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -6,6 +6,8 @@
//
//===--===//
+#if !defined(__wasm__)
arjunr2 wrote:
The WALI targets add the `__linux__` define, which is used under specific cases
in `assembly.h`. Figured since the hea
arjunr2 wrote:
Ping
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
arjunr2 wrote:
Added a few tests to clang for appropriate parsing
https://github.com/llvm/llvm-project/pull/156087
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/arjunr2 updated
https://github.com/llvm/llvm-project/pull/156087
>From cb996a12aa20c65980f620381731fad1622e0417 Mon Sep 17 00:00:00 2001
From: Arjun Ramesh
Date: Sat, 30 Aug 2025 01:01:02 -0400
Subject: [PATCH 1/2] Support for `wasm32-wali-linux-musl target` in `clang`,
`lld
arjunr2 wrote:
@carlocab Where should i be adding tests? And is it primarily for parsing of
the target?
Also it's unclear to me from the CI logs why the libcxx build is failing. Says
it received a user-cancelled signal -- was it manually aborted?
https://github.com/llvm/llvm-project/pull/1560
@@ -249,6 +249,9 @@ aliasname:
\
#define WEAK_ALIAS(name, aliasname)
#define NO_EXEC_STACK_DIRECTIVE
+#elif defined(__wasm__)
+#define NO_EXEC_STACK_DIRECTIVE
arjunr2 wrote:
Moved the header
https://github.com/arjunr2 updated
https://github.com/llvm/llvm-project/pull/156087
>From cb996a12aa20c65980f620381731fad1622e0417 Mon Sep 17 00:00:00 2001
From: Arjun Ramesh
Date: Sat, 30 Aug 2025 01:01:02 -0400
Subject: [PATCH] Support for `wasm32-wali-linux-musl target` in `clang`,
`lld`, a
arjunr2 wrote:
Removing changes from the linker to a separate RT leaves pretty much primarily
front-end changes.
WALI, as per the research paper and Rust, (currently) virtualizes the 64-bit
Linux syscall interfaces across many ISAs. It requires 64-bit long to adhere to
the Host-ABIs (i.e. x86
@@ -1200,6 +1225,36 @@ void Writer::createSyntheticInitFunctions() {
}
}
+void Writer::createMemoryGrowFunction() {
+ LLVM_DEBUG(dbgs() << "createMemoryGrowFunction\n");
+ assert(ctx.sym.memoryGrow);
+ std::string bodyContent;
+ {
+raw_string_ostream os(bodyContent);
https://github.com/arjunr2 created
https://github.com/llvm/llvm-project/pull/156087
This PR adds minimal support to the `clang` frontend, `lld`, and `libcxx` for
the
[WALI](https://doc.rust-lang.org/rustc/platform-support/wasm32-wali-linux.html)
target supported by the `rustc` toolchain
>Fro
21 matches
Mail list logo
