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

            Bug ID: 120525
           Summary: [16 Regression] ICE in vartrack building glibc
                    memusage.c for s390-linux-gnu
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jsm28 at gcc dot gnu.org
                CC: hjl at gcc dot gnu.org
  Target Milestone: ---
            Target: s390*-*-*

Created attachment 61565
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61565&action=edit
preprocessed source

Build the attached test (from glibc) with an s390x-linux-gnu compiler with
options: -m31 -fgnu89-inline -g -O2 -fPIC

commit 2da641d01700907d600ff9027ecfc82500342428
Author: H.J. Lu <hjl.to...@gmail.com>
Date:   Sun Jun 1 09:29:48 2025 +0800

    Move get_call_rtx_from to final.c

results in the following ICE from this test:

during RTL pass: vartrack
memusage.c: In function ‘update_data’:
memusage.c:223:1: internal compiler error: Segmentation fault
  223 | }
      | ^
0x1c75e9f internal_error(char const*, ...)
       
/notnfs/josmyers/glibc-manual/src/gcc/gcc/diagnostic-global-context.cc:517
0xda5cef crash_signal
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/toplev.cc:321
0x119242a prepare_call_arguments
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/var-tracking.cc:6277
0x119242a vt_initialize
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/var-tracking.cc:10297
0x1197863 variable_tracking_main_1
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/var-tracking.cc:10526
0x1197a0b variable_tracking_main()
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/var-tracking.cc:10579
0x1197a0b execute
        /notnfs/josmyers/glibc-manual/src/gcc/gcc/var-tracking.cc:10616
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

Reply via email to