--- Comment #4 from pinskia at gcc dot gnu dot org 2006-04-22 20:52 ---
This is not really that useful, the problem comes down to if the user messes up
(which is 90% of the time anyways), they get a crash in their program and blame
GCC. So exosing stuff like this is crazy to do really.
--- Comment #3 from rguenth at gcc dot gnu dot org 2006-02-21 10:06 ---
This doesn't really make any sense. Trying to over-educate a compiler usually
leads to worse code. Please rather try to isolate testcases where gcc does not
extract value range information it could extract.
--
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26369
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-02-20 02:09 ---
I don't understand why this is useful really as GCC now has VRP which will find
most of this information and remove code which is useless.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26369
--- Comment #2 from acahalan at gmail dot com 2006-02-20 04:00 ---
VRP (value range propagation, if I guess right) doesn't always have the data it
needs. Commonly, people split projects into multiple files and do not use
-fwhole-program to compile the project. This seems to be the norm
