Hopper __launch_bounds__ and setmaxnreg conflicts?

there does appear to be an issue if you use dynamic register allocation on Hopper and also force the maximum register count to be below a certain level. I don’t have further information.

TBH, I’m not sure why providing a dynamic register allocation of 232 makes sense if you are independently causing the compiler to limit register allocation to e.g. 168.

You haven’t provided a compilable test case. But if you want to do that, you may wish to file a bug.