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

            Bug ID: 93122
           Summary: ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1668
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: segher at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux-gnu
            Target: ppc64le-linux-gnu

I see the following ICE:

$ cat ice.i
fn1() { char s[4294967296]; }

$ ppc64le-linux-gnu-gcc -mfuture -mprefixed-addr -fstack-clash-protection ice.i
ice.i:1:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
    1 | fn1() { char s[4294967296]; }
      | ^~~
during RTL pass: dwarf2
ice.i: In function ‘fn1’:
ice.i:1:1: internal compiler error: in dwarf2out_frame_debug_expr, at
dwarf2cfi.c:1668
0x563858 dwarf2out_frame_debug_expr
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:1668
0x71bf1b dwarf2out_frame_debug
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:2169
0x71bf1b scan_insn_after
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:2518
0x71c8c8 scan_trace
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:2685
0x71ceb6 create_cfi_notes
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:2724
0x71ceb6 execute_dwarf2_frame
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:3093
0x71ceb6 execute
       
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64le/build/gcc/dwarf2cfi.c:3581
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

Reply via email to