------- Comment #5 from paolo dot carlini at oracle dot com 2009-10-20 18:12 ------- Ok, thanks, now I have a better picture. As a matter of fact, in *most* of the cases we should be *only* comparing pointers to the same object, I think this is the only case guaranteed to behave sanely under the current C++ rules (std::equal & co are more general). Thus, to summarize: __restrict__ normally should appear only for pointers not compared at all, please correct me if I'm wrong.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41763
