This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/15837] Optimization (of templatized functions?)
- From: "adruab at voria dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Jun 2004 06:38:33 -0000
- Subject: [Bug c++/15837] Optimization (of templatized functions?)
- References: <20040605201151.15837.adruab@voria.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From adruab at voria dot com 2004-06-06 06:38 -------
Hmmmmm, ok, so I changed a bunch of the functions to use p = (pointer)((char*)p
+ stride); and it seems to have fixed the mis-optimization. (it could just be
because the current function has to recurse another level, but I'm willing to
bet that it just doesn't get confused).
So my question now is why does gcc even allow the cast to (char*&)? If it will
get so confused shouldn't it tell me?
It's worth noting that the & part of the cast was a quick fix to get around
compiler errors that I was getting about aliasing... it seemed to work at the
time :P.
So I'll certainly keep that in mind when I'm designing future stuff (I didn't
write this really in the first place... so you know :P).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15837