[Bug lto/105121] New: ice in bp_unpack_string

[Bug lto/105121] New: ice in bp_unpack_string

[dcb314 at hotmail dot com]

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

            Bug ID: 105121
           Summary: ice in bp_unpack_string
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Created attachment 52731
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52731&action=edit
x86 object module

Recent gcc does this:

$ gcc src/bin/tolua.o src/bin/toluabind.o
lto1: internal compiler error: Segmentation fault
0xc94f99 crash_signal(int)
        ../../trunk.git/gcc/toplev.cc:322
0x772070 bp_unpack_string(data_in*, bitpack_d*)
        ../../trunk.git/gcc/data-streamer-in.cc:112
0xb89903 cl_optimization_stream_in(data_in*, bitpack_d*, cl_optimization*)
        /home/dcb/gcc/working/gcc/options-save.cc:13503
0xf1b7e0 streamer_read_tree_bitfields(lto_input_block*, data_in*, tree_node*)
        ../../trunk.git/gcc/tree-streamer-in.cc:558
0xad7186 lto_read_tree_1(lto_input_block*, data_in*, tree_node*)

The problem first seems to occur sometime between git hash 4cb935cb69f12088
and 1c7b110e1e44da0c.

[Bug lto/105121] ice in bp_unpack_string

[dcb314 at hotmail dot com]

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

--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Created attachment 52732
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52732&action=edit
x86 object module

[Bug lto/105121] ice in bp_unpack_string

[rguenth at gcc dot gnu.org]

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Are you sure you have object files compiled with the same compiler as you link
with?

[Bug lto/105121] ice in bp_unpack_string

[marxin at gcc dot gnu.org]

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-04-01
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING

[Bug lto/105121] ice in bp_unpack_string

[dcb314 at hotmail dot com]

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

--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Richard Biener from comment #2)
> Are you sure you have object files compiled with the same compiler as you
> link with?

I just compiled it again. Yes, I have the same compiler.
It looks like a mismatch in LTO readers and writers to me.

Would the .i file that is upstream of the .o file help ?

[Bug lto/105121] ice in bp_unpack_string

[marxin at gcc dot gnu.org]

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

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Note that we don't bump LTO bytecode version during the development of a GCC
release (stage1-4). Once we do a release, we keep eye on it.

[Bug lto/105121] ice in bp_unpack_string

[rguenth at gcc dot gnu.org]

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to David Binderman from comment #3)
> (In reply to Richard Biener from comment #2)
> > Are you sure you have object files compiled with the same compiler as you
> > link with?
> 
> I just compiled it again. Yes, I have the same compiler.
> It looks like a mismatch in LTO readers and writers to me.
> 
> Would the .i file that is upstream of the .o file help ?

Yes, that could possibly reproduce the issue.  Is the ICE happening in the
WPA process?  (add -v so you'd see that)

[Bug lto/105121] ice in bp_unpack_string

[dcb314 at hotmail dot com]

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

David Binderman <dcb314 at hotmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|WAITING                     |RESOLVED

--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Richard Biener from comment #5)
> Yes, that could possibly reproduce the issue.  Is the ICE happening in the
> WPA process?  (add -v so you'd see that)

It now fails to reproduce. Odd. Maybe the OS upgrade over the weekend
(Fedora 35 to 36 Beta) has something to do with it.

I am happy to close this one down as not reproducible.

I am not familiar with the WPA process, but I used -v and didn't see it
(gcc -v ... 2>&1 | grep -i wpa).

[Bug lto/105121] ice in bp_unpack_string

[rguenther at suse dot de]

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

--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 4 Apr 2022, dcb314 at hotmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105121
> 
> David Binderman <dcb314 at hotmail dot com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>          Resolution|---                         |WORKSFORME
>              Status|WAITING                     |RESOLVED
> 
> --- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
> (In reply to Richard Biener from comment #5)
> > Yes, that could possibly reproduce the issue.  Is the ICE happening in the
> > WPA process?  (add -v so you'd see that)
> 
> It now fails to reproduce. Odd. Maybe the OS upgrade over the weekend
> (Fedora 35 to 36 Beta) has something to do with it.
> 
> I am happy to close this one down as not reproducible.

No problem - just open a new bug if the issue pops up again.