[PATCH] D10414: Attach function attribute "arm-restrict-it" instead of passing arm-restrict-it as a backend-option

Jim Grosbach via cfe-commits cfe-commits at lists.llvm.org
Thu Sep 10 08:33:59 PDT 2015


grosbach added a comment.

In http://reviews.llvm.org/D10414#243056, @jmolloy wrote:

> Non-restricted IT blocks are indeed deprecated for ARMv8 in the ARMARM. But there are circumstances where you may still want to emit them - the biggest example being you're compiling for a CPU microarchitecture that you *know* doesn't have a performance penalty on non-restricted IT blocks. Restricted IT blocks can pessimize code quite badly in some circumstances, and allowing people to turn it off for their target if needed is very important, IMO.


Bother, email response isn't showing up in Phab. Reposting here so there's a record. Sorry for the duplication on-list.

If such microarchitectures exist, shouldn’t they be represented properly as a CPU in the backend and get the right setting by default?


http://reviews.llvm.org/D10414





More information about the cfe-commits mailing list