christoph
f618cfffaf
link mmap space to .text.wamr_mmap instead of .text.wamr_aot
2026-05-17 21:12:38 +02:00
christoph
177fe78618
call fail_marker_group1() in wasm_set_exception_local()
2026-05-11 16:45:16 +02:00
christoph
cda2009deb
baremetal: undo last undo
2026-04-21 22:32:38 +02:00
christoph
4e7aed33fe
baremetal: undo last change
2026-04-21 14:40:38 +02:00
christoph
1521011029
baremetal: place mmap memory region in .text segment
2026-04-16 22:56:24 +02:00
christoph
fd69a4e76e
baremetal: remove unnecessary functions
2026-03-11 18:13:02 +01:00
christoph
3318609c59
print buildtype/cflags/cxxflags on cmake configure
2026-03-11 15:11:00 +01:00
christoph
8fd8bc7b0f
typo
2026-03-08 14:31:17 +01:00
christoph
4c1c1875fc
baremetal: provide os_mmap/os_mremap for wamr aot_load_from_aot_file
2026-03-08 14:30:43 +01:00
christoph
ca3a01d7fc
baremetal: provide empty os_dcache_flush/os_icache_flush for wamr AOT build
2026-03-08 13:32:56 +01:00
christoph
0002e68b1c
baremetal: include string.h, stdlib.h, math.h for wamr AOT build
2026-03-08 13:24:22 +01:00
christoph
ef3b3eee85
baremetal: disable -mindirect-branch-register (requires gcc >5.4)
2026-03-08 12:56:59 +01:00
christoph
2bc885e0f9
baremetal: disable memcpy/memset/memmove
2026-03-08 12:28:55 +01:00
christoph
20376acee2
baremetal: second try (with i386-elf-gcc)
2026-03-05 00:53:45 +01:00
christoph
e426ea39e3
baremetal: add baremetal platform
2026-02-09 11:02:07 +01:00
christoph
888655330c
readme: add fork notice
2026-01-28 18:14:33 +01:00
liang.he and GitHub
8c18e3f68b
Bump version to 2.4.4 ( #4722 )
2025-11-25 07:11:08 +08:00
liang.he and GitHub
5149c4b11f
cherry picks few PRs from main branch ( #4725 )
...
* fix: update git clone branch for threads spec to main-legacy (#4687 )
* Fast-interp should report unsupport opcode when meeting simd opcode on non-posix platforms (#4723 )
2025-11-24 16:49:50 +08:00
liang.he and GitHub
de1d635efb
Merge commit from fork
...
* fix: remove SIMD prefix handling from interpreter and update opcode definitions
* test: add case for classic interpreter handling of unsupported SIMD opcodes
2025-11-24 14:37:46 +08:00
Zhenwei Jin and GitHub
ea7ac262a3
Merge commit from fork
2025-11-24 14:23:05 +08:00
liang.he and GitHub
d2a7b25409
Add inputs for optional WAMR releases in the release process workflow ( #4486 ) ( #4715 )
2025-11-24 13:27:01 +08:00
liang.he and GitHub
0e47872fb4
Bump version to 2.4.3 ( #4662 )
...
- relase notes
- bump version
2025-10-14 14:30:36 +08:00
8bd6794de6
libc-wasi: add missing pointer validations to socket functions ( #4611 ) ( #4665 )
...
* libc-wasi: add missing pointer validations to socket functions (#4611 )
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4463
the fix for sock_addr_resolve is incomplete.
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4610
* Sync from main branch
- wasi_sock_recv doesn't use src_addr
- check src_addr before coverting
* CI: use windows-2022 image for now (#4633 )
github is currently rolling out windows-2025 image.
for some reasons, the "path_symlink_trailing_slashes" test case in
wasi testsuite fails on windows-2025 image.
someone familar with windows need to investigate what was the
key difference between 2022 and 2025.
until that happens, this commit makes our CI use windows-2022 image.
cf.
https://github.com/bytecodealliance/wasm-micro-runtime/issues/4632
https://github.com/actions/runner-images/issues/12677
---------
Co-authored-by: YAMAMOTO Takashi <yamamoto@midokura.com >
2025-10-14 09:29:30 +08:00
liang.he and GitHub
6450d87299
bump version to 2.4.2 ( #4626 )
2025-09-15 17:11:18 +08:00
liang.he and GitHub
87fb38256b
Add release notes for WAMR-2.4.2 ( #4624 )
2025-09-15 15:35:58 +08:00
Liu Jia and GitHub
9530e4a310
Merge commit from fork
2025-09-15 15:19:51 +08:00
liang.he and GitHub
b124f70345
Bump version to 2.4.1 ( #4513 )
2025-07-28 20:49:11 +08:00
YAMAMOTO Takashi and GitHub
d298a66d38
bump AOT_CURRENT_VERSION for extended-const ( #4511 )
...
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4504
2025-07-27 14:39:35 +08:00
liang.he and GitHub
121232a995
Merge commit from fork
...
If `--addr-pool=1.2.3.4`, the runtime will return an error.
The value must be in the form of ADDRESS/MASK.
2025-07-27 14:38:56 +08:00
zhenweijin and Marcin Kolny
c080aa80d0
add a CL option to specify shared heap size
2025-07-22 05:01:14 +02:00
dependabot[bot] and Marcin Kolny
8ae3bf7080
build(deps): Bump github/codeql-action from 3.29.2 to 3.29.3
...
Bumps [github/codeql-action](https://github.com/github/codeql-action ) from 3.29.2 to 3.29.3.
- [Release notes](https://github.com/github/codeql-action/releases )
- [Commits](https://github.com/github/codeql-action/compare/v3.29.2...v3.29.3 )
---
updated-dependencies:
- dependency-name: github/codeql-action
dependency-version: 3.29.3
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com >
2025-07-22 04:53:52 +02:00
YAMAMOTO Takashi and GitHub
a780ffdc43
lib-socket: make getaddrinfo return EAI_ values ( #4498 )
...
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4464
2025-07-21 09:21:31 +08:00
liang.he and GitHub
952b35d11d
Add CI on Zephyr ( #4336 )
...
to run product-mini/platforms/zephyr/simple and
product-mini/platforms/zephyr/user-mode
Construct a T2 (star topology) for the current smoke test. This is not the
final topology, and we may modify it once we determine the optimal
configuration.
2025-07-21 09:21:01 +08:00
YAMAMOTO Takashi and GitHub
e4d2673a7c
wasi-nn: add a comment on load_by_name_with_config ( #4492 )
...
this api has been introduced by
https://github.com/bytecodealliance/wasm-micro-runtime/pull/3709
in which i couldn't find any explanations.
this comment is my best guess.
2025-07-17 09:50:49 +08:00
YAMAMOTO Takashi and GitHub
248e10b79e
nn-cli: add an option to use load_by_name ( #4490 )
...
by specifying a name for --load-graph.
for example,
```
--load-graph=name=foo
```
2025-07-17 09:47:20 +08:00
YAMAMOTO Takashi and GitHub
79408e59cc
wamr-wasi-extensions: document ( #4493 )
2025-07-17 09:44:47 +08:00
YAMAMOTO Takashi and GitHub
34f5d13444
doc/socket_api.md: some historical notes ( #4494 )
2025-07-17 09:43:54 +08:00
Liu Jia and GitHub
704aa3e7e5
modify macro related to simde when WASM_OP_SELECT_128 ( #4461 )
...
* remove macro of fast interpreter when WASM_OP_SELECT_128
* Modified some macros related to SIMDE
2025-07-17 08:04:41 +08:00
YAMAMOTO Takashi and GitHub
46d4e248bb
posix os_socket_accept: stop assuming socklen_t is unsigned int ( #4488 )
2025-07-17 08:04:13 +08:00
YAMAMOTO Takashi and Marcin Kolny
db942f3aaf
wasi_socket_ext.c: fix error reporting
...
do not return __WASI_ERRNO_xxx error code where 0/-1 is more appropriate.
most of them were not harmful because the value of
__WASI_ERRNO_SUCCESS is 0.
the one with __WASI_ERRNO_NOPROTOOPT in socket() is
a user-visible bug.
tested with wamr-wasi-extensions/samples/socket-tcp-udp.
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4474
2025-07-15 09:23:46 +02:00
YAMAMOTO Takashi and GitHub
2a952b371a
wasi_socket_ext.c: fix the number of getaddrinfo results ( #4466 )
...
the case of zero results was especially broken.
2025-07-14 13:12:32 +08:00
TianlongLiang and GitHub
b3158e643c
Fix typos ( #4472 )
...
* leave api name unchanged so don't break API
2025-07-14 13:12:08 +08:00
Liu Jia and GitHub
c8f7a7fc1a
fix regression running_config.json ( #4477 )
2025-07-14 13:08:58 +08:00
YAMAMOTO Takashi and GitHub
2c4a660c4c
posix os_socket_addr_resolve: relax compatibility check ( #4469 )
...
some getaddrinfo implementations sometimes return results with
ai_protocol=0.
cf. https://github.com/apache/nuttx/issues/16693
standard-wise, i couldn't find anything about ai_protocol in
susv4-2018 except the following text:
> The fields ai_family, ai_socktype, and ai_protocol shall be usable
> as the arguments to the socket() function to create a socket suitable
> for use with the returned address.
because ai_protocol is usually merely used to feed socket() and
socket() usually accepts 0, it's probably standard-wise ok for
getaddrinfo to return ai_protocol=0.
the major implementations of getaddrinfo (eg. kame) seem to return
specific values like ai_protocol=IPPROTO_TCP though.
anyway, for the purpose of this function, there is little point to
be strict on the host getaddrinfo behavior. this commit just relaxes
the check to be friendly to those getaddrinfo implementations.
2025-07-14 13:06:40 +08:00
YAMAMOTO Takashi and GitHub
53feadc2b0
lib-socket: implement getsockopt(SOL_SOCKET,SO_TYPE) ( #4458 )
...
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4456
2025-07-14 13:06:33 +08:00
YAMAMOTO Takashi and GitHub
5d48cfdbc0
introduce wasm_runtime_instantiate_ex2 ( #4444 )
...
* introduce wasm_runtime_instantiate_ex2
at this point, just a slightly inefficiant functionality
equivalent of wasm_runtime_instantiate_ex.
however, unlike wasm_runtime_instantiate_ex, this one is designed
to be extendable without breaking the user-visible ABI.
because the definition of InstantiationArgs2 is not exposed to
users, we can safely add new members to it.
this commit also makes wasm_runtime_instantiate_ex a wrapper
of wasm_runtime_instantiate_ex2.
if this goes well, maybe it's a good idea to apply a similar
pattern to RuntimeInitArgs, LoadArgs, SharedHeapInitArgs, etc.
i started with InstantiationArgs just because i happen to have
a need to extend it for wasi-nn.
cf.
https://github.com/bytecodealliance/wasm-micro-runtime/issues/4364
https://github.com/bytecodealliance/wasm-micro-runtime/issues/4331
* product-mini/platforms/posix: use wasm_runtime_instantiate_ex2
2025-07-14 13:06:23 +08:00
Zhenwei Jin and GitHub
65d3ffa7a4
add validation for recursive type count in loader ( #4440 )
2025-07-14 13:06:08 +08:00
liang.he and GitHub
47c7c85ac2
Bump version to 2.4.0 ( #4483 )
2025-07-14 11:06:03 +08:00
YAMAMOTO Takashi and GitHub
17be90d8f0
posix os_socket_addr_resolve: return the consistent max_info_size ( #4467 )
...
return the same value for max_info_size regardless of addr_info_size.
2025-07-10 13:42:57 +08:00
Zhenwei Jin and GitHub
9e92f5ebe1
fix a wamrc debug mode compile issue ( #4470 )
2025-07-10 08:29:31 +08:00