On Sat, 22 Feb 2025, Jonathan Wakely via Gcc-help wrote:
You didn't say how your configuring GCC but it looks like you're using
vtable-verify and so is the bug reporter. That's probably the cause, maybe
there's a bug in the vtv codegen.
Hey Jonathan. Thanks for your kind reply.
Here is the config.sh script that is run.
DIR_SRC=/opt/gcc/src
DIR_DST=/opt/gcc
CC="gcc" CXX="g++" CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS}" ${DIR_SRC}/configure \
--prefix=${DIR_DST} \
--exec-prefix=${DIR_DST} \
--datarootdir=${DIR_DST}/doc/share \
--datadir=${DIR_DST}/doc \
--docdir=${DIR_DST}/doc \
--htmldir=${DIR_DST}/doc \
--mandir=${DIR_DST}/doc/man \
--infodir=${DIR_DST}/doc/info \
--enable-languages=c,jit,c++ \
--enable-bootstrap \
--disable-multilib \
--enable-libstdcxx \
--enable-libstdcxx-debug \
--enable-libstdcxx-backtrace=yes \
--enable-shared \
--enable-host-shared \
--enable-plugin \
--enable-default-pie \
--enable-ld=yes \
--with-gnu-ld \
--with-linker-hash-style=gnu \
--enable-linker-build-id \
--enable-clocale=gnu \
--enable-gnu-indirect-function \
--enable-gnu-unique-object \
--enable-libssp \
--enable-lto \
--enable-gcov \
--enable-vtable-verify \
--enable-__cxa_atexit \
--enable-threads=posix \
--enable-tls \
--enable-werror \
--disable-unwind-exceptions \
--enable-install-libiberty \
--enable-c++-tools
This is the script that i've been using for the last 2 years and it's only in this week that this error has been encountered.
As things stand, is removing '--enable-vtable-verify' a good enough workaround ?
warm regards
Saifi.
