RFR: 8315066: Add unsigned bounds and known bits to TypeInt/Long [v13]

[Jasmine Karthikeyan]

On Thu, 5 Sep 2024 15:41:30 GMT, Quan Anh Mai <qamai at openjdk.org> wrote:

>> Hi,
>> 
>> This patch adds unsigned bounds and known bits constraints to TypeInt and TypeLong. This opens more transformation opportunities in an elegant manner as well as helps avoid some ad-hoc rules in Hotspot.
>> 
>> In general, a TypeInt/Long represents a set of values x that satisfies: x s>= lo && x s<= hi && x u>= ulo && x u<= uhi && (x & zeros) == 0 && (~x & ones) == 0. These constraints are not independent, e.g. an int that lies in [0, 3] in signed domain must also lie in [0, 3] in unsigned domain and have all bits but the last 2 being unset. As a result, we must normalize the constraints (tighten the constraints so that they are optimal) before constructing a TypeInt/Long instance.
>> 
>> This is extracted from #15440 , node value transformations are left for later PRs. I have also added unit tests to verify the soundness of constraint normalization.
>> 
>> Please kindly review, thanks a lot.
>> 
>> Testing
>> 
>> - [x] GHA
>> - [x] Linux x64, tier 1-4
>
> Quan Anh Mai has updated the pull request incrementally with two additional commits since the last revision:
> 
>  - rename tests
>  - more explanation

I think in most cases we expect `TypeInteger::make()` to have well-defined inputs and thus well-defined outputs, so I also think it would be good to keep the use sites as they were before for code cleanliness. For places where TOP is allowed there could be another function, maybe `TypeInteger::try_make()`, to signal explicitly that TOP is being handled by the callee code.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17508#issuecomment-2332224018