https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120266
Bug ID: 120266
Summary: newly introduced problems when using lto'ed
libstdc++-v3 in a static link
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: qubos at outlook dot de
Target Milestone: ---
Created attachment 61419
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61419&action=edit
linker output
ive upgraded from gcc 14.2.0 to gcc 15 and now see these warnings when linking.
the -Wodr is a common missinterpretation for when lto types mismatch. i have
build my entire toolchain with -flto -ffat-lto-objects and my target only
supports static linking.
while it is true that the _M_str field is missing i find it more worringly that
std::string gets resolved to two diffrent types, while from the little i digged
it should be the same because the detection logic wich too use just resolves to
a hard #define.
it might help when i say that my app uses -std=c++23 (i can only go to 20
because i allready used the modern features) while i left the standart library
at its default (i dont actually know where to change that/what the default is).
The resulting executable works but im alergic to getting warnings spit all over
my command line.
