(In reply to Iain Ireland [:iain] from comment #5) > It's a little silly that we're doing this optimization at all, since baseline presumably had a good reason for attaching `DoubleAddResult`. It's probably overkill to rip `TruncateAfterBailout` out completely, though. It is not silly at all, some code can be proven to work well only in Int32 range despite Baseline rightly thinking that each operation has to run with double math. This is what you are able to achieve with an optimizer which has more contextual information, than simply a single operation at a time.
Bug 1688136 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Iain Ireland [:iain] from comment #5) > It's a little silly that we're doing this optimization at all, since baseline presumably had a good reason for attaching `DoubleAddResult`. It's probably overkill to rip `TruncateAfterBailout` out completely, though. It is not silly at all, some code can be proven to work well in Int32 range despite Baseline rightly thinking that each operation has to run with double math. This is what you are able to achieve with an optimizer which has more contextual information, than simply a single operation at a time.