Displaying 2 results from an estimated 2 matches for "pr15026".
Did you mean:
pr15025
2013 Jan 21
2
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
...e tests are target independent, delete the triple.
> - If they aren't, sink them to a target-specific subdirectory so they're skipped in the absence of the target being built.
Filed llvm.org/pr15025.
> - Make a triple an error if there is not support for that target.
Filed llvm.org/pr15026.
I assume opt should completely ignore target triple when -mtriple is provided, potentially bypassing the error.
-Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130121/840d4c61/attachment.html>
2013 Jan 21
1
[LLVMdev] [llvm-commits] [llvm] r172534 - /llvm/trunk/test/Transforms/LoopStrengthReduce/post-inc-icmpzero.ll
...elete the triple.
>> - If they aren't, sink them to a target-specific subdirectory so they're skipped in the absence of the target being built.
>
> Filed llvm.org/pr15025.
>
>> - Make a triple an error if there is not support for that target.
>
> Filed llvm.org/pr15026.
>
>
> I assume opt should completely ignore target triple when -mtriple is provided,
>
> Yep.
>
> potentially bypassing the error.
>
> I would expect opt to error on an invalid '-mtriple' just as it would for an invalid triple in the IR....
Yes, that's...