This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/41763] valarray_array.h seems to overuse __restrict__
- From: "paolo dot carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 20 Oct 2009 18:12:40 -0000
- Subject: [Bug libstdc++/41763] valarray_array.h seems to overuse __restrict__
- References: <bug-41763-87@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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