[llvm-commits] [PATCH] llvm-stress fixes

[Gabor Greif]

Hal wrote:

> The current situation is not great, support for ppc128 in APFloat is
> currently broken, and while fixing it is on my TODO list, I have not
> really worked on it yet.

Something changed lately, as clang is ICEing on me when encountering  
a long double literal.
I am targetting PowerPC.

>
> If you edit APFloat.cpp to disable the relevant asserts then you can
> compile codes with long doubles in them (which is important for C++

Yes, I had to manually comment out an assertion in APFloat.cpp, to  
avoid the ICEs.

> codes that #include <complex>, for example), but any code that  
> actually
> uses long doubles will most likely output the wrong answer. Therefore,
> so long as some skeleton support exists, then there is no  
> regression in
> practice.

My sources do not actually resort to long doubles, but the <limits>  
header in our g++ installation does
have a specialization for 'long double' with literals in it. This  
seems to trigger the issue.

>
> I would be happy to move the relevant code into the frontend, but  
> while
> I imagine that in some ways this is very similar to how _Complex  
> double
> is handled, any assistance would be appreciated.

I gather that once the frontend is fixed the assert won't trigger any  
more?

Cheers,

     Gabor

>
> Thanks again,
> Hal


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20120416/372dfffc/attachment.html>