[PATCH] D60831: [DebugInfo at O2][LoopVectorize] pr39024: Vectorized code linenos step through loop even after completion

Hal Finkel via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Apr 17 12:08:28 PDT 2019


hfinkel added a subscriber: jmellorcrummey.
hfinkel added a comment.

In D60831#1470585 <https://reviews.llvm.org/D60831#1470585>, @Orlando wrote:

> In D60831#1470520 <https://reviews.llvm.org/D60831#1470520>, @hfinkel wrote:
>
> > How will this appear to profiling tools using PC sampling and using debug info to map the PC samples back to line numbers in the code?
>
>
> I brought this up in some offline discussions which all concluded that the impact on profilers would be small and the trade off for better debugging is worth it. The impact on profilers seems like it would be small because the middle block is only visited once after running through the vectorized loop.
>
> I am glad you asked because this concern gives rise to an argument for giving the middle block instructions line 0 instead, and i am interested in hearing other's opinions.


Interesting. The middle block just has the check for whether or not we need to run the remainder loop, right? I can definitely see this as kind of latch-like.

@jmellorcrummey , do you have an opinion on this?


Repository:
  rL LLVM

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D60831/new/

https://reviews.llvm.org/D60831





More information about the llvm-commits mailing list