[Bug c/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[Bug c/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[guido.hatzsis at yandex dot com]

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

--- Comment #1 from Guido Haztsis <guido.hatzsis at yandex dot com> ---
Created attachment 35861
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35861&action=edit
preproc source

[Bug c/66687] New: WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[guido.hatzsis at yandex dot com]

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

            Bug ID: 66687
           Summary: WPA link fau: internal compiler error: bytecode
                    stream: found non-null terminated string
           Product: gcc
           Version: lto
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: guido.hatzsis at yandex dot com
  Target Milestone: ---

Created attachment 35860
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35860&action=edit
res file

With gcc 5.1 is was possible to compile executables statically with with an
libc (musl) static library. It is no longer possible with 6.0



COLLECT_GCC_OPTIONS='-c' '-ffp-contract=off' '-fmath-errno' '-fsigned-zeros'
'-ftrapping-math' '-fno-trapv' '-fno-openmp' '-fno-openacc' '-mtune=generic'
'-march=x86-64' '-O2' '-fPIC' '-fno-exceptions' '-B' '/x32/gcc/stageN/./gcc/'
'-B' '/x32/build/host/x86_64-sb-linux-muslx32/bin/' '-B'
'/x32/build/host/x86_64-sb-linux-muslx32/lib/' '-v' '-save-temps'
'-mtune=generic' '-march=x86-64'
'-fltrans-output-list=/tmp/cctXDCnL.ltrans.out' '-fwpa'
'-fresolution=conftest.res'
 /x32/gcc/stageN/./gcc/lto1 -quiet -dumpbase crt1.o -mtune=generic
-march=x86-64 -mtune=generic -march=x86-64 -auxbase crt1 -O2 -version
-ffp-contract=off -fmath-errno -fsigned-zeros -ftrapping-math -fno-trapv
-fno-openmp -fno-openacc -fPIC -fno-exceptions
-fltrans-output-list=/tmp/cctXDCnL.ltrans.out -fwpa -fresolution=conftest.res
@/tmp/ccir6VzL

GNU GIMPLE (GCC) version 6.0.0 20150619 (experimental)
(x86_64-sb-linux-muslx32)
        compiled by GNU C version 5.1.0, GMP version 6.0.0, MPFR version 3.1.3,
MPC version 1.0.3
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU GIMPLE (GCC) version 6.0.0 20150619 (experimental)
(x86_64-sb-linux-muslx32)
        compiled by GNU C version 5.1.0, GMP version 6.0.0, MPFR version 3.1.3,
MPC version 1.0.3
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
lto1: internal compiler error: bytecode stream: found non-null terminated
string
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: fatal error: /x32/gcc/stageN/./gcc/xgcc returned 1 exit status
compilation terminated.
[Leaving LTRANS /tmp/ccO8tBym]
[Leaving LTRANS /tmp/cctXDCnL.ltrans.out]
/x32/build/host/x86_64-sb-linux-muslx32/bin/ld: fatal error: lto-wrapper failed

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[pinskia at gcc dot gnu.org]

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Are you sure that this is not a bug in musl?

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[guido.hatzsis at yandex dot com]

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

--- Comment #3 from Guido Haztsis <guido.hatzsis at yandex dot com> ---
Musl claims that they support LTO. Also all that I have changed was bumping gcc
from the 5.1_release tag to the latest overnight commit.

The res file doesn't even include libc.so (nor libc.a for a static build) which
is strange and musl has long claimed to support lto without fat objects.

(In reply to Andrew Pinski from comment #2)
> Are you sure that this is not a bug in musl?

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[pinskia at gcc dot gnu.org]

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
MUSL support is not included in GCC 5.x is another thing.  Also you are using
x32 which is not tested that much.

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[hjl.tools at gmail dot com]

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andrew Pinski from comment #4)
> MUSL support is not included in GCC 5.x is another thing.  Also you are
> using x32 which is not tested that much.

Can it be reproduced with x32 glibc?

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[guido.hatzsis at yandex dot com]

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

--- Comment #6 from Guido Haztsis <guido.hatzsis at yandex dot com> ---
(In reply to H.J. Lu from comment #5)
> (In reply to Andrew Pinski from comment #4)
> > MUSL support is not included in GCC 5.x is another thing.  Also you are
> > using x32 which is not tested that much.
> 
> Can it be reproduced with x32 glibc?

I am pretty sure it can be reproduced without any libc. Actually, for some
reason the libc.a file isn't even in the res file. This used to appear in the
5.1 version.

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[hjl.tools at gmail dot com]

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

--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Guido Haztsis from comment #6)
> I am pretty sure it can be reproduced without any libc. Actually, for some
> reason the libc.a file isn't even in the res file. This used to appear in
> the 5.1 version.

Does it mean it is musl specific and it can be reproduced with
musl for any targets?

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[pinskia at gcc dot gnu.org]

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

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Guido Haztsis from comment #6)
> (In reply to H.J. Lu from comment #5)
> > (In reply to Andrew Pinski from comment #4)
> > > MUSL support is not included in GCC 5.x is another thing.  Also you are
> > > using x32 which is not tested that much.
> > 
> > Can it be reproduced with x32 glibc?
> 
> I am pretty sure it can be reproduced without any libc. Actually, for some
> reason the libc.a file isn't even in the res file. This used to appear in
> the 5.1 version.

We are talking about the compiled GCC here.  Not the one being used with GCC at
this point.

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[rguenth at gcc dot gnu.org]

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

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Are you sure you produced all LTO bytecode with exactly the same compiler?
Reminds me to bump the LTO bytecode version again on trunk (it's still the same
as that on the GCC 5 branch...)

[Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string

[guido.hatzsis at yandex dot com]

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

--- Comment #10 from Guido Haztsis <guido.hatzsis at yandex dot com> ---
(In reply to Richard Biener from comment #9)
> Are you sure you produced all LTO bytecode with exactly the same compiler?
> Reminds me to bump the LTO bytecode version again on trunk (it's still the
> same
> as that on the GCC 5 branch...)

Was it bumped from 4 to 5? Yes, I am pretty sure I am using the same compliler.