https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949
Jörn Heusipp <manx-bugzilla at problemloesungsmaschine dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #3 from Jörn Heusipp <manx-bugzilla at problemloesungsmaschine dot
de> ---
> The c and c++ standard does not talks about how to invoke the compiler. POSIX
> does but that is a different standard all together.
I'm not asking gcc to implement whatever POSIX demands or deems reasonable from
a C compiler. I am asking -std=c11, or -std=c++17, which are ISO standards, for
which gcc by default only provides incomplete implementations while it would be
actually easy to provide complete implementations, and that would simplify
building.
If the standard does not demand anything, why are you even linking libc by
default then? There is no explanation or reasoning for the inconsistency
between different aspects of the standard.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
This is exactly the same problem, and as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358#c2 Andreas Schwab said:
"That doesn't mean that the mistake should be repeated."
I very much agree. And I very much want to see the earlier mistakes repaired as
well.
Consider the atomics issue to be also required to fix in order to close this
bug.
> Also gcc implements the compiler, it is up to the other vendor to implement
> the rest of the c library. Gcc does not implement printf either.
gcc libstdc++ implements std::thread. So what's your point again?
You did not address any of the standard violating behavior concerning
advertising thread support at all.
I did ask to not outright disregard this bug report. I suggest re-reading my
report, and at least try to acknowledge my reasoning, and reconsider.
Outright closing the bug feels just completely disrespectful.
These broken and surprising defaults, and even more surprising differences
between platforms that result from the broken defaults have cost the whole
industry presumably multi-million-dollar figures of money over the last decade,
and will continue to do so forever, if nothing gets actually fixed. And if you
want to disregard that argument because I cannot prove it, fine. I myself have
wasted probably days of my life with these quirks. I honestly cannot remember
which platform wants -pthread, which platform needs -lpthreads, which platform
needs -latomic, which platform wants -lm, which platform does not provide -lm
at all. It's a complete mess, and gcc is in the position to fix it, because it
*knows*.
Changing back to UNCONFIRMED so that *other* people can have a look.
