search for: ec7efb27

Hey guys, I found a performance regression in the X86 backend related to PR10884. In trunk, the frame pointer is always set up when an AVX register is used in a function. This is done in case 32-byte spill code is later introduced into the function and hence dynamic stack realignment is needed. Needless to say, it's a big hammer. This regression seems particularly painful in

> In trunk, the frame pointer is always set up when an AVX register is used in > a function. This is done in case 32-byte spill code is later introduced into > the function and hence dynamic stack realignment is needed. Needless to say, > it's a big hammer. This regression seems particularly painful in > small-to-medium sized routines that are called frequently in some codes.

...have any insight into why this behaviour changed sometime around the LLVM 3.0 release? I have not been able to find much history. Thanks again, Cameron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121023/ec7efb27/attachment.html>