[llvm] r177730 - R600: Use legacy (0 * anything = 0) MUL instructions for pow intrinsics

Chandler Carruth chandlerc at google.com
Tue Mar 26 11:21:41 PDT 2013


On Tue, Mar 26, 2013 at 11:16 AM, Christian König
<christian.koenig at amd.com>wrote:

> Completely agree to that, and I think adding test cases for new patterns,
> instructions important backend behaviour etc.. does indeed make allot of
> sense.
>
> But for example for the last change of our ELSE pseudo operation I don't
> even know how to cover that with llvm IR (except for adding compiled IR
> output of piglit and that's something around 25kb in size and covering
> allot of different things and not only that bug in specific).
>

Testcase reduction is a well understood endeavor though. Sometimes it
fails, but it is really important that you try everything you can to reduce
and distill a minimal test case to cover these types of bugs. Otherwise, no
one can maintain or update your backend with confidence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130326/6fe3d483/attachment.html>


More information about the llvm-commits mailing list