I still need to add tests, but I wanted to make sure first we agree this is the right way of using the new API.
Unfortunately, no tests fail if I remove the calls to the old API.
This is https://bugs.llvm.org/show_bug.cgi?id=33788
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Like I said in the other thread, you'll have a failing test in test/Other/new-pm-thinlto-defaults.ll I expect, I did.
lib/Transforms/Scalar/TailRecursionElimination.cpp | ||
---|---|---|
70 ↗ | (On Diff #107123) | Which one in particular? The build fails without OptimizationDiagnosticInfo.h included. |
305 ↗ | (On Diff #107123) | What do you mean exactly? Change the second parameter to be an unique identifier *within* the same file? |
lib/Transforms/Scalar/TailRecursionElimination.cpp | ||
---|---|---|
305 ↗ | (On Diff #107123) | Still probably makes sense to differentiate why, although that should be always uniquely identified by the string (I guess stats don't really want to grep in text messages, so, OK). |
lib/Transforms/Scalar/TailRecursionElimination.cpp | ||
---|---|---|
304 ↗ | (On Diff #107359) | Is this comment addition intentional? |
lib/Transforms/Scalar/TailRecursionElimination.cpp | ||
---|---|---|
304 ↗ | (On Diff #107359) | No, slipped through the cracks. I'll remove. |
LGTM once we clear the question below. Thanks!
lib/Transforms/Scalar/TailRecursionElimination.cpp | ||
---|---|---|
70 ↗ | (On Diff #107123) | OK :( |
305 ↗ | (On Diff #107123) | Yes, exactly. It allows to do stats based on the situation under we perform the optimization. I.e. if a case never triggers we don't want to pay for the analysis, etc. Looks like you convinced that it's worth using different names but then you didn't make the change... |