bnjbvr opened PR #1842 from regalloc-snapshotting
to master
:
Will need to come with https://github.com/bytecodealliance/regalloc.rs/pull/74, and a regalloc.rs bump as well. With this PR in regalloc.rs, this allows the serialization of function's IR graphs into a standalone IR that regalloc.rs can manipulate, allowing replay / perf-testing in regalloc.rs in a standalone fashion.
Right now, it requires the
enable-serde
feature to be set, an env variable "SERIALIZE_REGALLOC" set to anything, and it'll dump the IR graphs into the /tmp directory. I expect that we don't need a better user experience for this, since it's likely to be used very rarely in general.
bnjbvr requested cfallin and julian-seward1 for a review on PR #1842.
bnjbvr requested cfallin and julian-seward1 for a review on PR #1842.
bjorn3 submitted PR Review.
bjorn3 created PR Review Comment:
I think the
bincode
dependency should be behind a separate feature flag. You may want to useenable-serde
for clif ir serialization without using snapshotting.
cfallin submitted PR Review.
cfallin submitted PR Review.
cfallin created PR Review Comment:
Perhaps a low-cost UX improvement: can we take a base path from an environment variable, rather than hardcoding
/tmp
? (Perhaps just the value ofSERIALIZE_REGALLOC
, or call itSERIALIZE_REGALLOC_PATH
.) No need tomkdir
or anything fancy. Just would prefer not to have fixed filenames baked into the binary like this.
cfallin created PR Review Comment:
Agreed; let's have a separate
serialize-regalloc
feature or something similar.
julian-seward1 submitted PR Review.
bnjbvr updated PR #1842 from regalloc-snapshotting
to master
:
Will need to come with https://github.com/bytecodealliance/regalloc.rs/pull/74, and a regalloc.rs bump as well. With this PR in regalloc.rs, this allows the serialization of function's IR graphs into a standalone IR that regalloc.rs can manipulate, allowing replay / perf-testing in regalloc.rs in a standalone fashion.
Right now, it requires the
enable-serde
feature to be set, an env variable "SERIALIZE_REGALLOC" set to anything, and it'll dump the IR graphs into the /tmp directory. I expect that we don't need a better user experience for this, since it's likely to be used very rarely in general.
bnjbvr updated PR #1842 from regalloc-snapshotting
to master
:
Will need to come with https://github.com/bytecodealliance/regalloc.rs/pull/74, and a regalloc.rs bump as well. With this PR in regalloc.rs, this allows the serialization of function's IR graphs into a standalone IR that regalloc.rs can manipulate, allowing replay / perf-testing in regalloc.rs in a standalone fashion.
Right now, it requires the
enable-serde
feature to be set, an env variable "SERIALIZE_REGALLOC" set to anything, and it'll dump the IR graphs into the /tmp directory. I expect that we don't need a better user experience for this, since it's likely to be used very rarely in general.
bnjbvr updated PR #1842 from regalloc-snapshotting
to master
:
Will need to come with https://github.com/bytecodealliance/regalloc.rs/pull/74, and a regalloc.rs bump as well. With this PR in regalloc.rs, this allows the serialization of function's IR graphs into a standalone IR that regalloc.rs can manipulate, allowing replay / perf-testing in regalloc.rs in a standalone fashion.
Right now, it requires the
enable-serde
feature to be set, an env variable "SERIALIZE_REGALLOC" set to anything, and it'll dump the IR graphs into the /tmp directory. I expect that we don't need a better user experience for this, since it's likely to be used very rarely in general.
bnjbvr merged PR #1842.
Last updated: Nov 22 2024 at 16:03 UTC