Actually, skipping Ion compilation for just a subset of functions is going to be difficult here. Our second tier must be serializable. Baseline currently compiles a tier-up check in the prologue that won't work when the module is deserialized in the future. There may be other things that prevent baseline code from being serializable, we haven't tested this before. So it feels high-risk for something that should be a quick fix.
Bug 1921425 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Actually, skipping Ion compilation for just a subset of functions is going to be difficult here. Our second tier must be serializable. Baseline currently compiles a tier-up check in the prologue that won't work when the module is deserialized in the future. There may be other things that prevent baseline code from being serializable, we haven't tested this before. So it feels high-risk for something that should be a quick fix. I think it makes more sense to just disable Ion all together on a low end device.