abrown opened Issue #1245:
<!-- Please try to describe precisely what you would like to do in
Cranelift/Wasmtime and/or expect from it. You can answer the questions below if
they're relevant and delete this text before submitting. Thanks for opening an
issue! -->Feature
<!-- What is the feature or code improvement you would like to do in
Cranelift/Wasmtime? -->Remove the duplication of
map_reg
; it exists in bothwasmtime-debug
andcranelift-codegen
.Benefit
<!-- What is the value of adding this in Cranelift/Wasmtime? -->
Avoids duplicated code. See discussion in
https://github.com/bytecodealliance/wasmtime/commit/a9ca4c0f7b6e2db207acece2001b42b25efb08a0#r37665763 for context.Implementation
<!-- Do you have an implementation plan, and/or ideas for data structures or
algorithms to use? -->I think the best way to do this is likely to make
map-reg
public incranelift-codegen
and then re-publicize it throughwasmtime-environ
.wasmtime-debug
already has a dependency onwasmtime-environ
so this way we could reachmap_reg
and thus remove the duplicatedmap_reg
inwasmtime-debug
.Alternatives
<!-- Have you considered alternative implementations? If so, how are they
better or worse than your proposal? -->
- As @iximeow mentioned, there may be a way to write a new struct to do the mapping from cranelift registers to gimli registers
- We could import
cranelift-codegen
intowasmtime-debug
directly but thecranelift-codegen <- wasmtime-environ <- wasmtime-debug
seems cleaner
abrown edited Issue #1245:
<!-- Please try to describe precisely what you would like to do in
Cranelift/Wasmtime and/or expect from it. You can answer the questions below if
they're relevant and delete this text before submitting. Thanks for opening an
issue! -->Feature
<!-- What is the feature or code improvement you would like to do in
Cranelift/Wasmtime? -->Remove the duplication of
map_reg
; it exists in bothwasmtime-debug
andcranelift-codegen
.Benefit
<!-- What is the value of adding this in Cranelift/Wasmtime? -->
Avoids duplicated code. See discussion in https://github.com/bytecodealliance/wasmtime/commit/a9ca4c0f7b6e2db207acece2001b42b25efb08a0#r37665763 for context.Implementation
<!-- Do you have an implementation plan, and/or ideas for data structures or
algorithms to use? -->I think the best way to do this is likely to make
map-reg
public incranelift-codegen
and then re-publicize it throughwasmtime-environ
.wasmtime-debug
already has a dependency onwasmtime-environ
so this way we could reachmap_reg
and thus remove the duplicatedmap_reg
inwasmtime-debug
.Alternatives
<!-- Have you considered alternative implementations? If so, how are they
better or worse than your proposal? -->
- As @iximeow mentioned, there may be a way to write a new struct to do the mapping from cranelift registers to gimli registers
- We could import
cranelift-codegen
intowasmtime-debug
directly but thecranelift-codegen <- wasmtime-environ <- wasmtime-debug
seems cleaner
abrown assigned Issue #1245:
<!-- Please try to describe precisely what you would like to do in
Cranelift/Wasmtime and/or expect from it. You can answer the questions below if
they're relevant and delete this text before submitting. Thanks for opening an
issue! -->Feature
<!-- What is the feature or code improvement you would like to do in
Cranelift/Wasmtime? -->Remove the duplication of
map_reg
; it exists in bothwasmtime-debug
andcranelift-codegen
.Benefit
<!-- What is the value of adding this in Cranelift/Wasmtime? -->
Avoids duplicated code. See discussion in https://github.com/bytecodealliance/wasmtime/commit/a9ca4c0f7b6e2db207acece2001b42b25efb08a0#r37665763 for context.Implementation
<!-- Do you have an implementation plan, and/or ideas for data structures or
algorithms to use? -->I think the best way to do this is likely to make
map-reg
public incranelift-codegen
and then re-publicize it throughwasmtime-environ
.wasmtime-debug
already has a dependency onwasmtime-environ
so this way we could reachmap_reg
and thus remove the duplicatedmap_reg
inwasmtime-debug
.Alternatives
<!-- Have you considered alternative implementations? If so, how are they
better or worse than your proposal? -->
- As @iximeow mentioned, there may be a way to write a new struct to do the mapping from cranelift registers to gimli registers
- We could import
cranelift-codegen
intowasmtime-debug
directly but thecranelift-codegen <- wasmtime-environ <- wasmtime-debug
seems cleaner
abrown closed Issue #1245 (assigned to abrown):
<!-- Please try to describe precisely what you would like to do in
Cranelift/Wasmtime and/or expect from it. You can answer the questions below if
they're relevant and delete this text before submitting. Thanks for opening an
issue! -->Feature
<!-- What is the feature or code improvement you would like to do in
Cranelift/Wasmtime? -->Remove the duplication of
map_reg
; it exists in bothwasmtime-debug
andcranelift-codegen
.Benefit
<!-- What is the value of adding this in Cranelift/Wasmtime? -->
Avoids duplicated code. See discussion in https://github.com/bytecodealliance/wasmtime/commit/a9ca4c0f7b6e2db207acece2001b42b25efb08a0#r37665763 for context.Implementation
<!-- Do you have an implementation plan, and/or ideas for data structures or
algorithms to use? -->I think the best way to do this is likely to make
map-reg
public incranelift-codegen
and then re-publicize it throughwasmtime-environ
.wasmtime-debug
already has a dependency onwasmtime-environ
so this way we could reachmap_reg
and thus remove the duplicatedmap_reg
inwasmtime-debug
.Alternatives
<!-- Have you considered alternative implementations? If so, how are they
better or worse than your proposal? -->
- As @iximeow mentioned, there may be a way to write a new struct to do the mapping from cranelift registers to gimli registers
- We could import
cranelift-codegen
intowasmtime-debug
directly but thecranelift-codegen <- wasmtime-environ <- wasmtime-debug
seems cleaner
Last updated: Dec 23 2024 at 12:05 UTC