https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117477
--- Comment #4 from Dhruv Chawla <dhruvc at nvidia dot com> --- (In reply to Andrew Pinski from comment #3) > Do you have a testcase which comes from some real code that shows the issue > or is this just noticed from the small testcase you produced? Hi, I noticed this occurring in SPEC2017 while diffing changes before and after applying a patch. It does not happen very often though, it just piqued my curiosity. > As I mentioned it is a wash but only due to the pair allocation that aarch64 > can do. On other targets where the pair allocation does not happen, it is > usually a win. Should it still be preferred to do pair allocation on aarch64 then?
