Skip to content
This repository was archived by the owner on Jun 26, 2020. It is now read-only.

Limit redundant jump folding to only fold parameterless target blocks#972

Merged
sstangl merged 1 commit intobytecodealliance:masterfrom
sstangl:fold-non-phi
Sep 5, 2019
Merged

Limit redundant jump folding to only fold parameterless target blocks#972
sstangl merged 1 commit intobytecodealliance:masterfrom
sstangl:fold-non-phi

Conversation

@sstangl
Copy link
Contributor

@sstangl sstangl commented Sep 4, 2019

This is a better solution than #950.

It's obviously possible to do better than this, for example by folding edges that cannot possible be implicit phi nodes. The purpose of this phase is mostly to undo garbage blocks created by register allocation, so this simpler version serves that goal just fine.

@sstangl sstangl requested a review from nbp September 4, 2019 21:01
Copy link
Collaborator

@nbp nbp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds good to me, and solves the known issues.
@bnjbvr what is the policy for TODO in the code base?

@bnjbvr
Copy link
Member

bnjbvr commented Sep 5, 2019

There's no policies, so let's try to reproduce Spidermonkey's: a TODO = an issue open to discuss it and not forget about it? (There are many TODOs without matching issues at the moment, so it's fine to do best-effort here.)

@sstangl sstangl merged commit 850db85 into bytecodealliance:master Sep 5, 2019
@sstangl sstangl deleted the fold-non-phi branch September 5, 2019 14:21
@sstangl
Copy link
Contributor Author

sstangl commented Sep 5, 2019

There's already a Bugzilla issue still open for fixing this thoroughly. That's still in my dashboard and I won't forget about it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants