Closed
Description
Currently, the code just blindly multiplies the size, and can therefore return a nonsense result. (The behavior isn't really defined in the overflow case, but reasoning based on the overflowed computation is likely to lead to weird results.)
has code to compute the allocation size while conservatively checking for overflow; we should use similar logic, then make the inliner call getAllocationSize(). Maybe use the multiply-with-overflow helper from CheckedArithmetic.h instead of writing out that code.