[llvm-dev] OptBisect implementation for new pass manager (original) (raw)
Fedor Sergeev via llvm-dev llvm-dev at lists.llvm.org
Wed Sep 26 11:15:27 PDT 2018
- Previous message: [llvm-dev] OptBisect implementation for new pass manager
- Next message: [llvm-dev] OptBisect implementation for new pass manager
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 09/26/2018 08:57 PM, Philip Pfaffe wrote:
Well, I think we don't have a clear idea about new-PM codegen should work in general. Is this really something that concerns us right now? I dont believe it has anything to do specifically with New-PM. It is just a property of getting a "real code". There are passes that you cant skip if you want to get down to the runnable code.
regards, Fedor.
Philip On Wed, Sep 26, 2018 at 7:54 PM Friedman, Eli <efriedma at codeaurora.org_ _<mailto:efriedma at codeaurora.org>> wrote: On 9/26/2018 10:47 AM, Philip Pfaffe via llvm-dev wrote: > Hi Fedor, > > can you make an example where a pass actually needs to opt-out? > Because IMO, bisect should quite literally to DebugCounter-style skip > every step in every ::run method's loop. Passes should not even be > concerned with this. This isn't so much an issue for the optimization pipeline, but code generation involves some passes which are mandatory (e.g. isel). -Eli -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180926/4ac97ef3/attachment.html>
- Previous message: [llvm-dev] OptBisect implementation for new pass manager
- Next message: [llvm-dev] OptBisect implementation for new pass manager
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]