See as gcc ate my starbasic with -fno-strict-aliasing it prompted me to check if we still need -fno-strict-aliasing anyway given all the warning cleanups of the last year. The short answer is definitely 
, but it looks doable to make it possible, and I’ve gotten it to at least launch with -fstrict-aliasing which should be sufficient to do some measurements on it next week to see if there is any measurable difference. Unfortunately while I can (probably) make Ooo -fstrict-aliasing good there are a gadzillion warnings from the stlport headers used on i386 builds so unless stlport was bumped up to one of the later versions where the warnings are fixed (or stlport dropped and gcc’s stl used like we did for x86_64) then only non-i386 users could get the benefit.
Some other random thoughts to look at to see if they’d matter a damn are:
- revisit the symbol ordering stuff again where symbols used during startup are sorted side by side in the .so
- Use -fshort-wchar and make a shadow struct for OUString which can take a
wchar_t string to stick pre-created OUStrings into the rodata section. - somehow magically convert non-public symbols to a shorter name and/or reversed strings