Static src analysis of LibreOffice

John Smith lbalbalba at gmail.com
Mon Aug 6 12:03:49 PDT 2012


On Mon, Aug 6, 2012 at 9:57 AM, John Smith <lbalbalba at gmail.com> wrote:
> On Mon, Aug 6, 2012 at 9:08 AM, Stephan Bergmann <sbergman at redhat.com> wrote:
>>
>> That smells like "On recent Fedora 17, the included Clang (3.0) is unusable
>> due to clang++ chokes on <complex>. However, a home-built Clang 3.1 works
>> fine."
>> (<https://wiki.documentfoundation.org/Development/Building_LibreOffice_with_Clang#Setup>)
>>
>>
>> Stephan
>>
> Hrm. I did some googling, and I doubt that it's the same bug. This one
> occurs with something like this :
>
> # cat test.cpp
> #include <iostream>
>
> int main() {
>     std::cout << "Hello, world!" << std::endl;
> }
>
> # clang++ test.cpp -o test -std=gnu++11
> In file included from test.cpp:1:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/iostream:39:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/ostream:39:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/ios:40:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/bits/char_traits.h:40:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/bits/stl_algobase.h:65:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/bits/stl_pair.h:61:
> In file included from
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/bits/move.h:57:
> /usr/lib/gcc/i686-redhat-linux/4.7.0/../../../../include/c++/4.7.0/type_traits:256:39:
> error: use of undeclared identifier '__float128'
>     struct __is_floating_point_helper<__float128>
>                                       ^
> 1 error generated.
>
>
>
> I submitted a bug report : http://llvm.org/bugs/show_bug.cgi?id=13530
>
>
>
> John Smith.

Well it turns out that Clang (or any backends) doesn't support the
__float128 type (yet). Some possible workarounds are suggested in the
bug report.


- John Smith


More information about the LibreOffice mailing list