Displaying 2 results from an estimated 2 matches for "05590a18".
2016 May 12
1
LLVM Releases: Upstream vs. Downstream / Distros
...but there's nothing else
using it, so there's currently no need to force a common version of the API
between different projects there.
ttyl
bero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160512/05590a18/attachment.html>
2016 May 12
7
LLVM Releases: Upstream vs. Downstream / Distros
FWIW, for our ARM Compiler product, we follow top-of-trunk, not the releases.
Next to picking up new functionality quicker, it also allows us to detect regressions
in LLVM against our in-house testing quickly, not 6 months later. We find that when
we find a regression within 24 to 48 hours of the commit introducing it, it's much
cheaper to get it fixed.
In my opinion, it would be better