https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65828

Vittorio Zecca <zeccav at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zeccav at gmail dot com

--- Comment #6 from Vittorio Zecca <zeccav at gmail dot com> ---
(In reply to Steven Noonan from comment #1)
> If you want a nice tarball with a ready-to-go repro case, I've put it here:
> 
> https://www.uplinklabs.net/files/lto-65828.tar.xz
> 
> Should just be able to run something like:
> 
> $ /usr/lib/gcc/x86_64-unknown-linux-gnu/4.9.2/lto1 -quiet -dumpdir .libs/
> -dumpbase libglib-2.0.so.0.4400.0.wpa -mtune=generic -march=x86-64
> -mtune=generic -march=x86-64 -auxbase libglib_2_0_la-gallocator -O2 -O2
> -version -fno-trapv -fPIC
> -fltrans-output-list=libglib-2.0.so.0.4400.0.ltrans.out -fwpa
> -fresolution=libglib-2.0.so.res @ccWGeoup.args
> 
> from inside the extracted directory and see the issue.

I just run it with gcc-5.2.0 and I got the following error:

./repro.sh
+ /home/vitti/local/gcc-5.2.0/libexec/gcc/x86_64-unknown-linux-gnu/5.2.0/lto1
-quiet -dumpdir .libs/ -dumpbase libglib-2.0.so.0.4400.0.wpa -mtune=generic
-march=x86-64 -mtune=generic -march=x86-64 -auxbase libglib_2_0_la-gallocator
-O2 -O2 -version -fno-trapv -fPIC
-fltrans-output-list=libglib-2.0.so.0.4400.0.ltrans.out -fwpa
-fresolution=libglib-2.0.so.res @ccWGeoup.args
GNU GIMPLE (GCC) version 5.2.0 (x86_64-unknown-linux-gnu)
        compiled by GNU C version 5.2.0, GMP version 6.0.0, MPFR version 3.1.2,
MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU GIMPLE (GCC) version 5.2.0 (x86_64-unknown-linux-gnu)
        compiled by GNU C version 5.2.0, GMP version 6.0.0, MPFR version 3.1.2,
MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
lto1: fatal error: bytecode stream generated with LTO version 3.0 instead of
the expected 4.0
compilation terminated.

Reply via email to