------- Comment #33 from felix-gcc at fefe dot de 2007-01-21 13:53 -------
so now you give us... a straw man?
The range analysis has nothing to do with just assuming integers can't wrap.
But more to the point: the Intel compiler does not assume signed integers can't
wrap, and IT STILL PRODUCES MUCH FASTER CODE THAN GCC.
So all your hand waiving about how this optimization is good for performance is
utterly destroyed by the Intel compiler.
And please let me express my shock how you tell me to my face that the only
example where this optimization has measurable impact (I didn't actually try
it, but I will) is when it optimizes away range checks in C++ vectors. Which,
you know, exist solely because THERE ARE NO RANGE CHECKS IN C ARRAYS and, uh,
C++ is much better and people are told to use C++ vectors instead BECAUSE THEY
HAVE RANGE CHECKS and now you tell me that your optimization removes those.
Whoa, what an improvement, man. Now you convinced me. Not that the
optimization is useful, mind you, but that you are a marauding saboteur sent by
the evil minions at Microsoft on a mission to make open source software look
bad.
--
felix-gcc at fefe dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|WONTFIX |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
