There appears to be an inconsistent approach to the setting of the
InputSection eqClass in ICF which could cause incorrect equivalence
class equality.
It would appear that this has not caused any issues, but making it
consistent and therefore more deterministic feels safer.
There is indeed one existing 1U << 31 ... but there is no accompanying & 0x7fffffff I would expect.. So I start to wonder its merit..