Confusion about pointer values being compile-time constatns

Question

In C++, it is possible for pointer values to be compile-time constants. This is true, otherwise, non-type template parameters and constexpr won't work with pointers. However, as far as I know, addresses of functions and objects of static storage are known (at least) at link-time rather than compile-time. Following is an illustration:

main.cpp

#include <iostream>

template <int* p>
void f() { std::cout << p << '\n'; }

extern int a;

int main() {
    f<&a>();
}

a.cpp

int a = 0;

I'm just wondering how the address of a could possibly be known when compiling main.cpp. I hope somebody could explain this a little to me.

In particular, consider this

template <int* p, int* pp>
constexpr std::size_t f() { 
  return (p + 1) == (pp + 7) ? 5 : 10; 
}

int main() {
    int arr[f<&a, &b>()] = {};
}

How should the storage for arr be allocated?

PLUS: This mechanism seems to be rather robust. Even when I enabled Randomized Base Address, the correct output is obtained.

Answer 1

The compiler doesn't need to know the value of &a at compile time any more than it needs the value of function addresses.

Think of it like this: the compiler will instantiate your function template with &a as a parameter and generate "object code" (in whatever format it uses to pass to the linker). The object code will look like (well it won't, but you get the idea):

func f__<funky_mangled_name_to_say_this_is_f_for_&a>__:
   reg0 <- /* linker, pls put &std::cout here */
   reg1 <- /* hey linker, stuff &a in there ok? */
   call std::basic_stream::operator<<(int*) /* linker, fun addr please? */
   [...]

If you instantiate f<b&>, assuming b is another global static, compiler does the same thing:

func f__<funky_mangled_name_to_say_this_is_f_for_&b>__:
   reg0 <- /* linker, pls put &std::cout here */
   reg1 <- /* hey linker, stuff &b in there ok? */
   call std::basic_stream::operator<<(int*) /* linker, fun addr please? */
   [...]

And when your code calls for calling either of those:

fun foo:
   call f__<funky_mangled_name_to_say_this_is_f_for_&a>__ 
   call f__<funky_mangled_name_to_say_this_is_f_for_&b>__

Which exact function to call is encoded in the mangled function name. The generated code doesn't depend on the runtime value of &a or &b. The compiler knows there will be such things at runtime (you told it so), that's all it needs. It'll let the linker fill in the blanks (or yell at you if you failed to deliver on your promise).

---

For your addition I'm afraid I'm not familiar enough about the constexpr rules, but the two compilers I have tell me that this function will be evaluated at runtime, which, according to them, makes the code non-conforming. (If they're wrong, then the answer above is, at least, incomplete.)

template <int* p, int* pp>
constexpr std::size_t f() { 
  return (p + 1) == (pp + 7) ? 5 : 10; 
}

int main() {
    int arr[f<&a, &b>()] = {};
}

clang 3.5 in C++14 standards conforming mode:

$ clang++ -std=c++14 -stdlib=libc++ t.cpp -pedantic
t.cpp:10:10: warning: variable length arrays are a C99 feature [-Wvla-extension]
  int arr[f<&a, &b>()];
         ^
1 warning generated.

GCC g++ 5.1, same mode:

$ g++ -std=c++14 t.cpp -O3 -pedantic
t.cpp: In function 'int main()':
t.cpp:10:22: warning: ISO C++ forbids variable length array 'arr' [-Wvla]
   int arr[f<&a, &b>()];

Answer 2

As far as I know, the variables of static storage and functions are stored simply as symbols/place holders in the symbol table while compiling. It is in the linking phase when the place holders are resolved.

The compiler outputs machine code keeping the placeholders intact. Then the linker replaces the placeholders of the variables / functions with their respective memory locations. So in this case too, if you just compile main.cpp without compiling a.cpp and linking with it, you are bound to face linker error, as you can see here http://codepad.org/QTdJCgle (I compiled main.cpp only)