https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111019
--- Comment #12 from Sławomir Fraś <boskidialer at gmail dot com> ---
$ /opt/gcc-745ec1/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/opt/gcc-745ec1/bin/g++
COLLECT_LTO_WRAPPER=/opt/gcc-745ec1/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-w
rapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/opt/gcc-745ec1
--enable-languages=c,
c++,fortran,go --disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230818 (experimental) (GCC)
With the above version i was unable to reproduce the issue using the full tests
suite, in that sense i am considering this issue to be resolved.
Only issue that i was facing here was caused by the usage of gcc 14.0 instead
of gcc 12.3 so i had to suppress following warning:
/home/dashboard/factorio/libraries/Agui/GenericTargetable.hpp:55:18: error:
storing the address of local variable ‘helper’ in
‘*&this_5(D)->D.195240.D.130047.D.129358.agui::GenericTargetable::agui::GenericTargetBase.agui::GenericTargetBase::next’
[-Werror=dangling-pointer=]
Basically we are using local variables which are registering in some heap
allocated classes temporarily but they are aware of that so in the destructor
they correctly unlink themselves to avoid heap allocated objects from having
pointers to deallocated local variables. This check is a false positive that
does not work in our project so i had to suppress it. I think this may be a
separate thing so in order to not pollute this bug report i wont provide more
details unless you want more of it.
