Previously we would allow promotion even if the byval/inalloca
attributes on the call and the callee didn't match.
It's ok if the byval/inalloca types aren't the same. For example, LTO
importing may rename types.
Fixes PR51397.
Paths
| Differential D107998
[CallPromotion] Check for inalloca/byval mismatch ClosedPublic Authored by aeubanks on Aug 12 2021, 2:33 PM.
Details Summary Previously we would allow promotion even if the byval/inalloca It's ok if the byval/inalloca types aren't the same. For example, LTO Fixes PR51397.
Diff Detail
Unit TestsFailed
Event Timelineaeubanks mentioned this in D107770: [CallPromotion] Fix byval/inalloca handling.Aug 12 2021, 2:35 PM This revision is now accepted and ready to land.Aug 13 2021, 10:12 AM This revision was landed with ongoing or failed builds.Aug 13 2021, 4:56 PM Closed by commit rGc19d7f8af032: [CallPromotion] Check for inalloca/byval mismatch (authored by aeubanks). · Explain Why This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 366115 llvm/lib/Transforms/Utils/CallPromotionUtils.cpp
llvm/test/Transforms/PGOProfile/mismatched-byval.ll
llvm/test/Transforms/PGOProfile/mismatched-inalloca.ll
|