Displaying 2 results from an estimated 2 matches for "548x".
Did you mean:
548
2017 Oct 26
3
RFC: Switching to the new pass manager by default
...ctually meant asserts enabled. Thus, this
issue can show up in either a debug or release build, if asserts are
enabled.
On 10/26/2017 4:05 PM, Chad Rosier via llvm-dev wrote:
>
> Chandler/All,
>
> We've just started testing the new pass manager this week and we ran
> into a 548x slowdown (i.e., 6.28s to 3443.83s) for one of the files
> from SPEC2017/blender. The issue arises only in debug builds due to
> the numerous calls to RefSCC::verify() and SCC::verify() in the
> LazyCallGraph implementation. Would it make sense to start
> predicating these calls wi...
2017 Oct 18
18
RFC: Switching to the new pass manager by default
Greetings everyone!
The new pass manager is getting extremely close to the point where I'm not
aware of any significant outstanding work needed, and I'd like to see what
else would be needed to enable it by default. Here are the current
functionality I'm aware of outstanding:
1) Does not do non-trivial loop unswitching. Majority of this is in
https://reviews.llvm.org/D34200 but will