tree e85dc66872720f30a77441917358d7546dce8086
parent 0755d6ce821cb1ca1e5a5bdf3a8d1d63b08da86d
author Alastair Donaldson <afdx@google.com> 1559856155 +0100
committer GitHub <noreply@github.com> 1559856155 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJc+YQbCRBK7hj4Ov3rIwAAdHIIACnxeLw/d2udFLQ0dnxNELV3
 dKy1wbSmm0gYWG1PIiB4UTiHqFQqWDO8lW40tHl2QH61TI/+tEgsGqGt2Uf7GhNv
 HeWi48iy8+bnKjwvORdl5m9NQh8h77ugi7Mpi+zWMhBrmzUBi3V84hRAaZnBPmj7
 1l/bJf/GR2HNctnfqPIIsfVpMTef29r8UdZ04tyU7pGzi4eKEe4/IKZxXTeL7cwa
 zu2HQWSoRXkzTfMDpbPPXOkqX4dDbpVJ48Qkoh5+HAOqaejziK/SopUqsKUnhXHc
 YIU8Dw8voTCWgiwFbWZpcO+obg1WlsWJRB9heRxIKdmF9Fb+zsgRNMcOPO+7t6U=
 =sO0y
 -----END PGP SIGNATURE-----
 

Add transformation to replace a boolean constant with a numeric comparison (#2659)

The transformation can, for example, replace "true" with "12.0 > 6.0",
if constants for those floating-point values are available.

This introduces a new 'id use descriptor' structure, which provides a
way to describe a particular use of an id, and which will be heavily
used in future transformations.  Describing an id use is trivial if
the use occurs in an instruction that itself generates an id, but is
less straightforward if the id of interest is used by an instruction
such as OpStore that does not have a result id.  The 'id use
descriptor' structure caters for such cases.