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

--- Comment #3 from dave.anglin at bell dot net ---
On 2024-02-23 4:09 a.m., doko at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114062
>
> --- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> ---
> this is seen when building with -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64
> and applying the proposed patch from PR114065.
I built gcc-13 12.2.0 package successfully outside buildd on mx3210.  c8000a
buildd
failed for the third time building gcc-14:

In file included from ../../src/gcc/hash-table.h:248,
                  from ../../src/gcc/coretypes.h:498,
                  from ../../src/gcc/analyzer/call-details.cc:24:
../../src/gcc/vec.h:2314:51: internal compiler error: in pop, at vec.h:1056
  2314 | vec<T, va_heap, vl_ptr>::contains (const T &search) const
       |                                                   ^
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/hppa-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
 -I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include 
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-fno-PIE -c   -g -O2 -fno-checking -DIN_GCC    -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual  -fno-common  -DHAVE_CONFIG_H -fno-PIE -I. -Ianalyzer
-I../../src/gcc -I../../src/gcc/analyzer -I../../src/gcc/../include 
-I../../src/gcc/../libcpp/include -I../../src/gcc/../libcody 
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace   -o analyzer/call-string.o
-MT analyzer/call-string.o -MMD -MP -MF analyzer/.deps/call-string.TPo
../../src/gcc/analyzer/call-string.cc
0xd2415f cp_lexer_rollback_tokens
        ../../src/gcc/cp/parser.cc:1438
0xda56cf cp_parser_parse_definitely
        ../../src/gcc/cp/parser.cc:35798
0xd73367 cp_parser_direct_declarator
        ../../src/gcc/cp/parser.cc:23928
0xd72fc3 cp_parser_declarator
        ../../src/gcc/cp/parser.cc:23773
0xd7116f cp_parser_init_declarator
        ../../src/gcc/cp/parser.cc:23257
0xd9b2b7 cp_parser_single_declaration
        ../../src/gcc/cp/parser.cc:33240
0xd98937 cp_parser_template_declaration_after_parameters
        ../../src/gcc/cp/parser.cc:32793
0xd9a93f cp_parser_explicit_template_declaration
        ../../src/gcc/cp/parser.cc:33066
0xd9aa1f cp_parser_template_declaration_after_export
        ../../src/gcc/cp/parser.cc:33085
0xd5d9fb cp_parser_template_declaration
        ../../src/gcc/cp/parser.cc:18171
0xd546af cp_parser_declaration
        ../../src/gcc/cp/parser.cc:15502
0xd54cd3 cp_parser_toplevel_declaration
        ../../src/gcc/cp/parser.cc:15594
0xd2e99b cp_parser_translation_unit
        ../../src/gcc/cp/parser.cc:5279
0xe09b87 c_parse_file()
        ../../src/gcc/cp/parser.cc:51202
0x1200863 c_common_parse_file()
        ../../src/gcc/c-family/c-opts.cc:1311
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-14/README.Bugs> for instructions.
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/hppa-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
 -I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include 
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-fno-PIE -c   -g -O2 -fno-checking -DIN_GCC    -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual  -fno-common  -DHAVE_CONFIG_H -fno-PIE -I. -Ianalyzer
-I../../src/gcc -I../../src/gcc/analyzer -I../../src/gcc/../include 
-I../../src/gcc/../libcpp/include -I../../src/gcc/../libcody 
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace   -o analyzer/call-summary.o
-MT analyzer/call-summary.o -MMD -MP -MF analyzer/.deps/call-summary.TPo
../../src/gcc/analyzer/call-summary.cc
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/hppa-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
 -I/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/include 
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-hppa-linux-gnu/libstdc++-v3/libsupc++/.libs 
-fno-PIE -c   -g -O2 -fno-checking -DIN_GCC    -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual  -fno-common  -DHAVE_CONFIG_H -fno-PIE -I. -Ianalyzer
-I../../src/gcc -I../../src/gcc/analyzer -I../../src/gcc/../include 
-I../../src/gcc/../libcpp/include -I../../src/gcc/../libcody 
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace   -o analyzer/checker-event.o
-MT analyzer/checker-event.o -MMD -MP -MF analyzer/.deps/checker-event.TPo
../../src/gcc/analyzer/checker-event.cc
The bug is not reproducible, so it is likely a hardware or OS problem.

Helge, would you please disable building gcc (gcc-13 and gcc-14) on c8000 sap
buildd.

I believe gcc builds okay on the qemu buildds although it takes some time.

It's highly unlikely that the build failures on c8000a are a gcc issue.  They
all relate to memory
allocation.

Dave

Reply via email to