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

Coredump: ability to mark local/stack values as optimized out #198

Closed
xtuc opened this issue Feb 7, 2023 · 0 comments · Fixed by #199
Closed

Coredump: ability to mark local/stack values as optimized out #198

xtuc opened this issue Feb 7, 2023 · 0 comments · Fixed by #199

Comments

@xtuc
Copy link
Contributor

xtuc commented Feb 7, 2023

From bytecodealliance/wasmtime#5732 (comment).

The coredump format should allow marking local and stack values are missing / optimized out.
xtuc added a commit to xtuc/tool-conventions that referenced this issue Feb 8, 2023
@xtuc
Coredump: add local/stack value typing
5b35102 
This change adds typing to local and stack values. Technically the type
isn't strictly necessary as DWARF should indicate how to interpret the values.

However, using types allows us to represent the lack of value, because
it has been optimized out and more complex values like reference types.

Closes WebAssembly#198
xtuc added a commit to xtuc/tool-conventions that referenced this issue Feb 8, 2023
@xtuc
Coredump: add local/stack value typing
bbd6ec8 
This change adds typing to local and stack values. Technically the type
isn't strictly necessary as DWARF should indicate how to interpret the values.

However, using types allows us to represent the lack of value, because
it has been optimized out and more complex values like reference types.

Closes WebAssembly#198
xtuc added a commit to xtuc/tool-conventions that referenced this issue Feb 8, 2023
@xtuc
Coredump: add local/stack value typing
d46cd28 
This change adds typing to local and stack values. Technically the type
isn't strictly necessary as DWARF should indicate how to interpret the values.

However, using types allows us to represent the lack of value, because
it has been optimized out and more complex values like reference types.

Closes WebAssembly#198
@xtuc xtuc mentioned this issue Feb 8, 2023
Merged
xtuc added a commit to xtuc/tool-conventions that referenced this issue Feb 9, 2023
@xtuc
Coredump: add local/stack value typing
6fc92e1 
This change adds typing to local and stack values. Technically the type
isn't strictly necessary as DWARF should indicate how to interpret the values.

However, using types allows us to represent the lack of value, because
it has been optimized out and more complex values like reference types.

Closes WebAssembly#198

This change also updates links after switching to a new repo.
dschuff pushed a commit that referenced this issue Feb 16, 2023
@xtuc
Coredump: add local/stack value typing (#199)
fc2df94 
This change adds typing to local and stack values. Technically the type
isn't strictly necessary as DWARF should indicate how to interpret the values.

However, using types allows us to represent the lack of value, because
it has been optimized out and more complex values like reference types.

Closes #198

This change also updates links after switching to a new repo.
@xtuc xtuc mentioned this issue Feb 17, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Coredump: add local/stack value typing xtuc/tool-conventions
1 participant
@xtuc