https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #21 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to cqwrteur from comment #20) > (In reply to Jonathan Wakely from comment #19) > > (In reply to cqwrteur from comment #16) > > > That does not work in the real-world since your libstdc++'s freestanding > > > header never works correctly, (you get compilation errors). > > > > Try reporting a bug about *that* next time (except don't, I don't want any > > more stupidity from you). > > Let me be more clear. That would be a welcome change from your usual nonsense. > 1. Freestanding C++ in the current situation is very problematic. (You do > not have memcpy, you do not have std::move. You do not have std::forward. > You do not have std::addressof(). you do not have std::array.) However, you > have an exception handling support. But no dependency on stdio. > 2. What's the point of reporting a bug when building libstdc++ with GNU So it can be fixed, duh. > newlib just works much better and you have an entire hosted toolchain that > will not break compilation? The only problem is that you never enable EH. > I did report bugs before. However, it was not fixed. I am not going to try > it again tbh since newlib works just fine. Great. So build with --disable-libstdcxx-verbose as well and stop complaining about a feature that other people find useful. Maybe we should make that the default for --with-newlib builds. That might be a useful improvement. More useful than your usual hyperbole and timewasting anyway.
