Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change SignalHandlers.h to SignalHandlers.hpp #42

Merged
merged 1 commit into from
Jan 15, 2019
Merged

Change SignalHandlers.h to SignalHandlers.hpp #42

merged 1 commit into from
Jan 15, 2019

Conversation

buckle2000
Copy link
Contributor

Closes #41

@sunfishcode
Copy link
Member

The change looks good, thanks! That said, it's not obvious to me why this fixes #41, since <stdbool.h> is a C header file which ought to be available to C code.

@sunfishcode sunfishcode merged commit 01ed463 into bytecodealliance:master Jan 15, 2019
kubkon pushed a commit that referenced this pull request Nov 7, 2019
@marmistrz
Implement fd_filestat_get for all platforms (#42)
89fbde2 
* Implement fd_filestat_get for all platforms

* Remove an old comment

* Remove panics from the syscall wrappers

* Return WASI error type

* Reuse Metadata if possible to save syscalls.

* Refactor the change for two separate fd_filestat_get_impl

* Refactor error handling
grishasobol pushed a commit to grishasobol/wasmtime that referenced this pull request Nov 29, 2021
@pepyakin
Memory units (bytecodealliance#42)
483736b 
* Initial implementation

* Not use grow as it is makes debug builds very slow

* Use Pages::BYTE_SIZE for LINEAR_MEMORY_PAGE_SIZE

* Tidy docs.

* Use memory_units from git.
howjmay pushed a commit to howjmay/wasmtime that referenced this pull request Jan 24, 2022
@alexcrichton
Fix a memory cycle when creating *Func (bytecodealliance#44)
986b514 
The global map for storing `*Func` objects previously stored `*Store`,
but that creates a reference cycle between the Rust and the Go heaps
which can't be cleaned up. Instead this commit updates the logic to
instead use a "thread local" variable to temporarily store the current
freelist during a call and moves the storage outside of the global
variables. This should allow everything to get garbage collected as
usual.

Closes bytecodealliance#42
pchickey pushed a commit to pchickey/wasmtime that referenced this pull request May 16, 2023
@sunfishcode
Implement host file flags and type functions. (bytecodealliance#42)
18a8d26 
This gets us another step closer to running the Wasmtime tests.
dhil pushed a commit to dhil/wasmtime that referenced this pull request Jul 13, 2023
@frank-emrich
Compile-time option for bypassing ContinuationReference creation (byt…
3cb2dda 
…ecodealliance#42)
dhil added a commit to dhil/wasmtime that referenced this pull request Jul 13, 2023
@dhil
Improve compile option for disabling the continuation linearity check.
ddc9f27 
This patch improves upon bytecodealliance#42. In addition it renames the flag, so to build a compiler & runtime without linearity checking one has to supply the following:

```shell
$ cargo build --features=default,unsafe_disable_continuation_linearity_check
```
dhil added a commit to dhil/wasmtime that referenced this pull request Jul 13, 2023
@dhil
Improve compile option for disabling the continuation linearity check.
6d61fcc 
This patch improves upon bytecodealliance#42. In addition it renames the flag, so to build a compiler & runtime without linearity checking one has to supply the following:

```shell
$ cargo build --features=default,unsafe_disable_continuation_linearity_check
```
dhil added a commit to dhil/wasmtime that referenced this pull request Jul 13, 2023
@dhil
Improve compile option for disabling the continuation linearity check. (
ea8b1a7 
bytecodealliance#47)

* Improve compile option for disabling the continuation linearity check.

This patch improves upon bytecodealliance#42. In addition it renames the flag, so to build a compiler & runtime without linearity checking one has to supply the following:

```shell
$ cargo build --features=default,unsafe_disable_continuation_linearity_check
```
dhil added a commit to dhil/wasmtime that referenced this pull request Nov 3, 2023
@dhil
Reliably construct backtraces when stack switching is enabled. (bytec…
9fce0fc 
…odealliance#42)

This patch is a follow up on PR bytecodealliance#35. It partially addresses issue
presence of stack switching as older frame pointers are not guaranteed
to be greater than the current frame pointer (e.g. tracing across
stack boundaries).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@buckle2000 @sunfishcode