Arm Development Studio forum NEON intrinsics arguments

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NEON intrinsics arguments

Note: This was originally posted on 30th August 2011 at http://forums.arm.com

I'm using the return value from an intrinsic as an argument for another one like below:

int16x8_t final_vec = vorrq_s16(vandq_s16(final_mask_vec, bad_vec), vandq_s16(vmvnq_s16(final_mask_vec), good_vec));

Is that a good idea? Is there anything against using this kind of construct?
I guess the temporary vector returned from one of the inner intrinsics calls still has to be "assigned" to a
NEON register(at least that's my feeling the compiler will do). What happens if in a loop I try to optimize
using intrinsics I exceed the number of the actual Q registers NEON has available?