Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


Hi All!

This week started with me trying to understand the problem in bridges/
module with clang toolchain.
There were two major errors which I had to solve--

The first problem was with clang being rejecting incompatible declarations
of the same extern "C" function under different namespaces.
With the help of Miklos, I came across one of the earlier commits of sberg,
which fixed the same issue for linux_x86-64. I understood the changes in
that commit and replicated those for gcc_arm bridge.

The second problem required me to understand some portion of the exception
handling implementation in G++ and Clang compilers.
Exception handling in LO for arm is implemented taking into account the GCC
toolchain. Based on the differences between the two implementations, I did
some changes to the code but turned out they were not sufficient. I built
the source and ran the app but it crashed with an SIGSEGV error,  I'm
currently working on backtracing it.

Apart from these major errors, I did some minor tweaks to suppress the
warnings about unused variables, unattended fall throughs etc. and also
tackled a linker error with integer multiplication overflow check in
include/o3tl/safeint.hxx.

Progress of clang switch task can be found here:
https://gerrit.libreoffice.org/#/c/38438/

Regards,
Gautam Prajapati
IRC Nick - brainbreaker[m]

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.