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

            Bug ID: 91404
           Summary: [10 Regression] internal compiler error: Segmentation
                    fault
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

On x86-64, when building 483.xalancbmk in SPEC CPU 2006, r273857 caused:

$ gcc  -S -DSPEC_CPU -DNDEBUG  -DAPP_NO_THREADS -DXALAN_INMEM_MSG_LOADER -I.
-Ixercesc -Ixercesc/dom -Ixercesc/dom/impl -Ixercesc/sax
-Ixercesc/util/MsgLoaders/InMemory -Ixercesc/util/Transcoders/Iconv
-Ixalanc/include -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C
-DPROJ_SAX2 -DPROJ_DOM -DPROJ_VALIDATORS -DXML_USE_NATIVE_TRANSCODER
-DXML_USE_INMEM_MESSAGELOADER -O2    -DSPEC_CPU_LP64  -DSPEC_CPU_LINUX    
XPath.cpp  -ffast-math
./PlatformDefinitions.hpp:66:35: internal compiler error: Segmentation fault
   66 |  #define XALAN_CPP_NAMESPACE_END  }
      |                                   ^
0xfbc09f crash_signal
        ../../src-trunk/gcc/toplev.c:326
0xb26383 lookup_page_table_entry
        ../../src-trunk/gcc/ggc-page.c:632
0xb26383 ggc_set_mark(void const*)
        ../../src-trunk/gcc/ggc-page.c:1531
0xd69c41 gt_ggc_mx_symtab_node(void*)
        /export/gnu/import/git/gcc-test-spec-lto/bld/gcc/gtype-desc.c:1302
0xee468d gt_ggc_ma_order
        ./gt-passes.h:31
0xee468d gt_ggc_ma_order
        ./gt-passes.h:26
0xcf6115 ggc_mark_root_tab
        ../../src-trunk/gcc/ggc-common.c:77
0xcf631c ggc_mark_roots()
        ../../src-trunk/gcc/ggc-common.c:94
0xb26d05 ggc_collect()
        ../../src-trunk/gcc/ggc-page.c:2201
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.

It doesn't fail with pre-processed file.

Reply via email to