[PATCH] D76193: [ValueTracking] Use assumptions in computeConstantRange.

Florian Hahn via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Apr 1 04:24:55 PDT 2020


fhahn added a comment.

In D76193#1927889 <https://reviews.llvm.org/D76193#1927889>, @nikic wrote:

> In D76193#1924399 <https://reviews.llvm.org/D76193#1924399>, @fhahn wrote:
>
> > That's a neat site. It looks very useful. Do you know if there's any more information about the site?  Is there a way to also check the patches together with D76228 <https://reviews.llvm.org/D76228>?
> >
> > With respect to the regression, I am a bit surprised that there are seem to be quite a few assumptions encoded using assume() from clang. I'll check.
>
>
> If you push a branch that starts with `perf/` to your fork <https://github.com/fhahn/llvm-project>, it should get picked up. I've also done a run with the additional patch: Individual commits <http://llvm-compile-time-tracker.com/index.php?branch=nikic%2Fperf%2Ffhahn-basicaa-constant-range-2> and all three combined <http://llvm-compile-time-tracker.com/compare.php?from=b9f1b8be1cb02f6159c27856e33996a7edb2bd18&to=18d82b328cc00f9cb3102a62cb61ac66272f5e75&stat=instructions>.


Awesome I tried with a branch and it seems to get picked up.

Did you consider open-sourcing the scripts/tooling, e.g. as part of LNT/test-suite/llvm-zorg or as standalone project? It would be great if it would be possible to spin up separate instances, to not overload lvm-compile-time-tracker.com ;)


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D76193





More information about the llvm-commits mailing list