[Bug libstdc++/100057] There are no freestanding C++

["unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #20 from cqwrteur <unlvsur at live dot com> ---
(In reply to cqwrteur from comment #19)
> (In reply to Richard Biener from comment #18)
> > So first of all --disable-hosted-libstdcxx doesn't work up to its standard? 
> > But maybe it's just specifics for x86_64-elf and other targets work fine
> > here.
> > 
> > Did you try forcing -ffreestanding for target library build with
> > CFLAGS_FOR_TARGET="-g -O2 -ffreestanding" ../configure ....?
> > 
> > Because libstdc++ may not be the only target library with the stdint.h issue.
> 
> dude never works.
> 
> That is why people are not using C++ for writing operating system.
> 
> Also why people like Linux hate C++ so much.
> 
> Anyone who attempted to write OS in C++ feel the same way. That is why C is
> still the only language for writing OS kernel.
> 
> You give reasons for Trolls like Richard Stallman and Linus to attack this
> language

https://forum.osdev.org/viewtopic.php?f=8&t=23947

The same freaking issue was been mentioned 10 years ago. No one actually tries
to fix this until I come.

There are a lot of historical issues with GCC implementations and I tried to
submit patches to fix them.

like BUFSIZ macro on windows, which is wrong for 30 years (just fixed in GCC11
because I reported the bug).
addcarry. (still does not work)

The freestanding C++ is an absolute joke. Not just because of the reason of
exception handling. The GCC team did a horrible job in the past.

Of course LLVM is even worse, but I am not going to trash talk about that here.