Jonathan Wakely via Gcc <gcc@gcc.gnu.org> writes: > On Fri, 5 Jul 2024 at 17:02, Xi Ruoyao via Gcc <gcc@gcc.gnu.org> wrote: >> >> On Fri, 2024-07-05 at 17:53 +0200, Alejandro Colomar wrote: >> > At least, I hope there's consensus that while current GCC doesn't warn >> > about this, ideally it should, which means it should warn for valid uses >> > of strtol(3), which means strtol(3) should be fixed, in all of ISO, >> > POSIX, and glibc. >> >> It **shouldn't**. strtol will only violate restrict if it's wrongly >> implemented, or something dumb is done like "strtol((const char*) &p, >> &p, 0)". >> >> See my previous reply. > > Right, is there a valid use of strtol where a warning would be justified? > > Showing that you can contrive a case where a const char* restrict and > char** restrict can alias doesn't mean there's a problem with strtol.
I still don't understand why it'd be appropriate for GCC and glibc to override this without it even being *brought to* the committee, either.
