-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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.
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
Create the new pass manager pipelines #46175
Conversation
d9514db
to
437c374
Compare
437c374
to
5487563
Compare
} else { | ||
MPM.addPass(RemoveNI()); | ||
} | ||
MPM.addPass(LowerSIMDLoop()); // TODO why do we do this twice |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While translating our pass pipeline over to NewPM, I noticed that we're calling for LowerSIMDLoop to run twice in the pipeline if we're running at O1 or below. Is there a particular reason for this double run?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I think we should only run it once
The SparseArrays Win64 segfault is unrelated to this PR, and this PR doesn't really turn on any interesting functionality that could cause it anyways. |
* Create basic NewPM structures * Replace incidental uses of the legacy pass manager with the new pass manager * Run the MC emitter
* Create basic NewPM structures * Replace incidental uses of the legacy pass manager with the new pass manager * Run the MC emitter
This PR does 2 things to move us closer to using NewPM everywhere:
Much of the content of this PR was cribbed from #44365, just separating it out to merge the more unobjectionable parts first
Fix #44987.