Can I build the benchmarks as either 32- or 64- bit binaries?
For the Medium input set, we expect the individual ranks to run within 2GB of memory per rank, given at least 4 ranks. On some systems, this is sufficient to fit in a 32-bit address space so the binaries can be compiled as 32-bit. Note that on some of the benchmarks, as you increase the number of ranks, the memory requirement decreases in each of the ranks, so you may be able to run a benchmark as a 32-bit binary by adding more nodes to the system. You can choose to compile your peak binaries as 32- or 64- bit individually for each benchmark. For base you will need to compile all benchmarks of the same language the same way, unless you can demonstrate that this is not possible. In this case 64-bits must be chosen as the default, and benchmarks which cannot be run 64-bit can be compiled 32-bit.
For the Medium input set, we expect the individual ranks to run within 2GB of memory per rank, given at least 4 ranks. On some systems, this is sufficient to fit in a 32-bit address space so the binaries can be compiled as 32-bit. Note that on some of the benchmarks, as you increase the number of ranks, the memory requirement decreases in each of the ranks, so you may be able to run a benchmark as a 32-bit binary by adding more nodes to the system. You can choose to compile your peak binaries as 32- or 64- bit individually for each benchmark. For base you will need to compile all benchmarks of the same language the same way, unless you can demonstrate that this is not possible. In this case 64-bits must be chosen as the default, and benchmarks which cannot be run 64-bit can be compiled 32-bit.
