------- Comment #5 from rguenth at gcc dot gnu dot org 2007-11-15 15:40 -------
That is, a certain class of operations (like COMPLEX_EXPR) do not fulfil the
constraint that if one operand is UNDEFINED the result is UNDEFINED as well.
For example MIN_EXPR <INT_MIN, UNDEFINED>, or MAX_EXPR <INT_MAX, UNDEFINED>
are of such kind as well. No idea if we want a white-list here instead.
BIT_AND_EXPR <UNDEFINED, 0> is also not UNDEFINED.
(all of the above not with actual constants as defined arg, but VARYING ones)
I have a patch.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2007-11-15 10:21:31 |2007-11-15 15:40:13
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34099
