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

            Bug ID: 113712
           Summary: lto crash: when building 641.leela_s peek with
                    Example-gcc-linux-x86.cfg (SPEC2017 1.1.9)
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: lehua.ding at rivai dot ai
  Target Milestone: ---

Commond:
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/build/x64-debug-gcc2-simple/install/bin/g++
    -std=c++03 -m64     -fprofile-generate  -g -Ofast -march=native -flto      
 -fopenmp -DSPEC_OPENMP  FullBoard.o KoState.o Playout.o TimeControl.o
UCTSearch.o GameState.o Leela.o SGFParser.o Timing.o Utils.o FastBoard.o
Matcher.o SGFTree.o TTable.o Zobrist.o FastState.o GTP.o MCOTable.o Random.o
SMP.o UCTNode.o                      -o leela_s

Backtrace:
lto1: internal compiler error: in add_symbol_to_partition_1, at
lto/lto-partition.cc:215
0x462426 add_symbol_to_partition_1
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto-partition.cc:215
0x4625f9 add_symbol_to_partition
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto-partition.cc:270
0x462274 add_symbol_to_partition_1
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto-partition.cc:180
0x4625f9 add_symbol_to_partition
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto-partition.cc:270
0x46325a lto_balanced_map(int, int)
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto-partition.cc:566
0x450653 do_whole_program_analysis
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto.cc:553
0x450870 lto_main()
       
/work/home/lding/open-source/riscv-gnu-toolchain-upstream/dev/gcc2/gcc/lto/lto.cc:666
Please submit a full bug report, with preprocessed source.
Please include the complete backtrace with any bug report.

Reply via email to