search for: specfii

...he value is modified. This means loads from restricted pointers and non-restricted pointers can alias, as can loads from restricted pointers and other restricted pointers. They even given an example of this, and declare it legal. Restrict is sadly not that useful in the way the standard actually specfiies.

On Aug 22, 2007, at 3:48 PM, Duncan Sands wrote: > Hi Christopher, > >> If A and B are function arguments then there is no "based on" >> relationship between pointer expressions A+0 and B+0. This is because >> changing one of the pointers, A for example, to point to a copy of >> the object it points to would change the value of the pointer >>

...} As neither p nor q is "based on" r, the alias analysis is free to determine that they do not alias r given the restrict nature of q and q. And neither q nor r is used to modify the object it points to. > Restrict is sadly not that useful in the way the standard actually > specfiies. In practice I have actually found the restrict qualifier to be critical to generating efficient code in certain circumstances. These cases were specialized compute codes, however, not typically user apps. Cheers -- Chris