Our out-of-tree custom aliasing solution for the HPC# Burst compiler here at Unity makes use of the ExternalAAWrapperPass infrastructure to insert our custom aliasing resolution into the core of LLVM. This is great for all cases except for function inlining, where because createLegacyPMAAResults does not make use of ExternalAAWrapperPass, when we have a definite no-alias result within a function that won't be propagated to the calling function during inlining.
This commit just rectifies this oversight by adding the missing dependency.
I wasn't sure how to test this given that the only in-tree user of the ExternalAAWrapperPass infrastructure is the AMDGPU backend - I'd appreciate guidance on that facet of this change.
I don't feel very strongly about it, but IMO it's generally preferable to have braces around multi-line statements.