https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51663
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
Cross-referencing PR gdb/25684 - "gdb testing with gcc -flto" (
https://sourceware.org/bugzilla/show_bug.cgi?id=25684 ).
Ideally there would be a way to enable the lto infrastructure without actually
optimizing, such that when running the gdb testsuite with and without flto and
comparing results, any regression would indicate something that needs fixing.
In the current situation, each individual regression needs investigation
whether something needs fixing or whether the failure is just an optimization
artifact. And due to the fact there are optimizations, there are thousands of
such regressions.
