Duane Ryan wrote: > Well, in general it's good coding to follow strict aliasing. In > conjunction with the restrict keyword, this can result in a) more stable > code, and b) faster code, because the compiler doesn't have to worry > about potential aliasing. > > How about this: is there any reason why we SHOULD allow potential > aliasing? > > Also, for more information, see here: > http://www.cellperformance.com/mike_acton/2006/05/demystifying_the_restrict_keyw.html What a cool link! Thank you very much. I think somebody tossed me that link a week ago or two, but I didn't take the time to read it back then. But now that I did, I have a solid motivation to take a close look at some pixel munging code in the app_server... :-) Best regards, -Stephan