https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109274
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #54742|0 |1
is obsolete| |
--- Comment #6 from Andrew Macleod <amacleod at redhat dot com> ---
Created attachment 54743
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54743&action=edit
new patch
Before floating point relations were added, we tried to sanitize
value-relation records to not include non-sensensical records... ie
x != x or x < x. Instead, we made a VREL_VARYING record with no
operands.
When floating point relations were supported, some of these were no
longer non-sensical, AND we expanded the use of value_relation records
into GORI.
As a result, this sanitization is no longer needed. The Oracle
does not create records with op1 == op2, so its only within GORI
that these records can exist, and we shouldn't try to interpret them.
The bug occurs because the "sanitized" records doesn't set op1 and op2, and
changes the relation to VARYING.. and we have a record so expected the
operands it to be set the way they were just set.
We should not be setting a VREL_VARYING record if asked to set something else.
