Am Montag, dem 08.07.2024 um 17:01 +0200 schrieb Alejandro Colomar: > On Mon, Jul 08, 2024 at 10:30:48AM GMT, David Malcolm wrote:
... > And then have it mean something strict, such as: The object pointed to > by the pointer is not pointed to by any other pointer; period. > > This definition is already what -Wrestrict seems to understand. One of the main uses of restrict is scientific computing. In this context such a definition of "restrict" would not work for many important use cases. But I agree that for warning purposes the definition of "restrict" in ISO C is not helpful. > > > Later, I added a new -Wanalyzer-overlapping-buffers warning in GCC 14, > > which simply has a hardcoded set of standard library functions that it > > "knows" to warn about. > > Hmmm, so it doesn't help at all for anything other than libc. Ok. > > > Has the C standard clarified the meaning of 'restrict' since that > > discussion? Without that, I wasn't planning to touch 'restrict' in > > GCC's -fanalyzer. > > Meh; no they didn't. There were examples added in C23 and there are now several papers being under discussion. > I understand. That's why I don't like innovations > in ISO C, and prefer that implementations innovate with real stuff.
