On 26/09/2020 08:24, Rene Engelhard wrote: > Am 25.09.20 um 12:54 schrieb Michael Meeks: >> I wonder if, ABI-wise, we could static link sal with libmerged for the >> purpose of LTO and get away with it =) > > I disagree. =) >> Since there is no real C++ ABI, and no exported symbols, particuarly >> exceptions there - that could work across platforms and give a big win. Its possible the easy wins come from static linking the C / sal library and LTO'ing it. >> Ideally we could get down the chain from the grey (cf. attached >> picture) to the bottom there: cppuhelper, xmlreader, cppu, salhelper, sal. > > Nope :) Yep - bit of a packaging nightmare; then again ... I -think- if those libraries are used by C++ plugins only - and these are always loaded after the versions included in the core (easy to guarentee if it's all loaded there). We could continue to install copies of these, but have all the symbols static linked / merged into a big libmerged without real problems. > With the expense of overhauling the whole package, merging all those > libs into Yep, would suck. Of course if it is 2x as fast perhaps worth looking at but we need numbers. Thanks for the feedback, Michael. -- michael.meeks@xxxxxxxxxxxxx <><, GM Collabora Productivity Hangout: mejmeeks@xxxxxxxxx, Skype: mmeeks (M) +44 7795 666 147 - timezone usually UK / Europe _______________________________________________ LibreOffice mailing list LibreOffice@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/libreoffice