[Bug libstdc++/106735] New: tens of thousands of errors in C++ library

[Bug libstdc++/106735] New: tens of thousands of errors in C++ library

[seurer at gcc dot gnu.org]

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

            Bug ID: 106735
           Summary: tens of thousands of errors in C++ library
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

I am seeing over 42,000 new errors after some recent trunk commit in the C++
library or usage of the C++ library.

A couple of examples (they are all or mostly like these):

FAIL: g++.dg/gomp/pr88182.C  -std=gnu++98 (test for excess errors)
Excess errors:
/home/seurer/binutils/install/bin/ld:
/home/seurer/gcc/git/build/gcc-trunk/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs/libstdc++.so:
undefined reference to `std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > std::operator+<char,
std::char_traits<char>, std::allocator<char> >(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&, char const*)'


FAIL: g++.dg/ext/tmplattr4.C  -std=c++98 (test for excess errors)
Excess errors:
/home/seurer/binutils/install/bin/ld:
/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs/libstdc++.so:
undefined reference to `std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > std::operator+<char,
std::char_traits<char>, std::allocator<char> >(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&, char const*)'


I have a bisect running and will report if it finds a culprit.

[Bug libstdc++/106735] tens of thousands of errors in C++ library

[mpolacek at gcc dot gnu.org]

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-08-24
     Ever confirmed|0                           |1
                 CC|                            |mpolacek at gcc dot gnu.org
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed, I see it too (vanilla trunk).

[Bug libstdc++/106735] tens of thousands of errors in C++ library

[seurer at gcc dot gnu.org]

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

--- Comment #2 from seurer at gcc dot gnu.org ---
It it causing so many error messages that emails to the gcc test results list
from my autotesters are being rejected as they are 3.9MB in size.

[Bug libstdc++/106735] tens of thousands of errors in C++ library

[mpolacek at gcc dot gnu.org]

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jwakely.gcc at gmail dot com

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think it started with r13-2175-g0b7c9254998b3f.

[Bug libstdc++/106735] tens of thousands of errors in C++ library

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Target Milestone|---                         |13.0
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org

[Bug libstdc++/106735] tens of thousands of errors in C++ library

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reverted at r13-2192-ge5428086c2c8daf69e5916dd5016d1e7b85d3f0d

lxo identified the problem:
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600268.html
But I'll revisit when the sun is up and figure out why my testing didn't see
it.