https://sourceware.org/bugzilla/show_bug.cgi?id=27231
--- Comment #9 from Jakub Jelinek <jakub at redhat dot com> --- (In reply to H.J. Lu from comment #6) > GCC 11 also generates: > > 00000176 0000000000002097 (base address) > 0000017f 0000000000002097 00000000000020f8 > 00000182 000000000000213d 000000000000213d (start == end) > 00000187 000000000000233f 0000000000002346 > 0000018c <End of list> > > .LLRL171: > .byte 0x5 > .quad .LBB2156 > .byte 0x4 > .uleb128 .LBB2156-.LBB2156 > .uleb128 .LBE2156-.LBB2156 > .byte 0x4 > .uleb128 .LBB2157-.LBB2156 > .uleb128 .LBE2157-.LBB2156 > .byte 0x4 > .uleb128 .LBB2158-.LBB2156 > .uleb128 .LBE2158-.LBB2156 > .byte 0 > > This triggers: > > if ((low_pc == 0 && high_pc == 0) || low_pc == high_pc) > return FALSE; > > in read_rnglists(). Is this a GCC 11 bug? No, binutils bug. There is nothing special about 0 low or high pc or low_pc == high_pc in .debug_rnglists. The list termination is rather DW_RLE_end_of_list. -- You are receiving this mail because: You are on the CC list for the bug.
