This is not an "array pointer" as there's no such thing. This is an array declaration and will go around your code with a tag attached: shall you access say  you should get an out of bounds.
An array is an array. Your confusion likely arises from the fact it will become a pointer at the earliest convenience.
Back to your point.
If you use this array in a fully predictable way (say, based on a loop index from a unrollable loop) odds are this array won't exist. The compiler might inline it in instruction immediates. Or not. It really depends on a case by case. If the addressing is complicated, it will overspill to some memory (usually global) to support the relative addressing.
So the best thing to do is to try the static analyzer or even better, profile the running program (as the driver might give different results).