[llvm-commits] [compiler-rt] r165913 - /compiler-rt/trunk/lib/ubsan/ubsan_value.cc

Richard Smith richard at metafoo.co.uk
Thu Nov 29 15:06:57 PST 2012


On Thu, Nov 29, 2012 at 2:42 PM, Richard Smith <richard at metafoo.co.uk>wrote:

> On Thu, Nov 29, 2012 at 1:53 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>> On Sun, Oct 14, 2012 at 4:53 PM, Richard Smith
>> <richard-llvm at metafoo.co.uk> wrote:
>> > Author: rsmith
>> > Date: Sun Oct 14 18:53:37 2012
>> > New Revision: 165913
>> >
>> > URL: http://llvm.org/viewvc/llvm-project?rev=165913&view=rev
>> > Log:
>> > Provide a slightly more helpful diagnostic if
>> -fcatch-undefined-behavior finds
>> > a problem with __int128 arithmetic but the runtime was not built with
>> __int128
>> > support.
>>
>> Would it be possible for the test cases that depend on this would be
>> marked as untested/xfail/something on platforms that don't support it?
>>
>
> It should be possible, yes. It's a little tricky (it depends on both the
> target and on the compiler used to build compiler-rt), but I'll have a look.
>

Situation should be improved in r168955 -- tests for __int128 are disabled
if we don't support __int128 on the target, but will still fail if the
target supports __int128 but the compiler which built compiler-rt does not.
That might actually be a benefit -- the test failure indicates that
compiler-rt has been built badly...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20121129/f8b1d57e/attachment.html>


More information about the llvm-commits mailing list