[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-09 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 --- Comment #5 from Martin Liška --- Hi. I've just tried to build libreoffice: commit abadeb7a4a76e8ea6ec449f3ea564abf8d52a231 Author: Maxim Monastirsky Date: Sun Feb 28 16:30:58 2016 +0200 Unused defines Change-Id: Idc31e498a7223e

[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-07 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 Markus Trippelsdorf changed: What|Removed |Added CC||hubicka at ucw dot cz --- Comment

[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-07 Thread kabel at blackhole dot sk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 --- Comment #3 from Marek Behun --- Created attachment 37892 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37892&action=edit sanitizer-output.txt

[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-07 Thread kabel at blackhole dot sk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 --- Comment #2 from Marek Behun --- (In reply to Markus Trippelsdorf from comment #1) Does not happen with -O0, does with -O1, -O2, -O3. When gengal.bin is compiled with -O0 -fsanitize=undefined, then in runs successfully, but the sanitizer pri

[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-06 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c++/70112] [lto] Segmentation fault in Libreoffice's program gengal.bin when build with LTO

2016-03-06 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70112 --- Comment #1 from Markus Trippelsdorf --- There is too little information to be useful. At least please build with debugging info enabled and find out exactly what is going on. Next build with -fsanitize=undefined to see if any undefined behavi