On Mon, 11 Jan 2016, Thomas Schwinge wrote: > Alexander, would you please also submit a fix for that for nvptx-tools' > nvptx-run.c? (Or want me to do that?)
I can do that, along with another small change I used for -mgomp testing. > Going further, for both GCC's libgomp and nvptx-tools' nvptx-run, would > it make sense to have a way to restrict code generation to a specific SM > version for testing purposes? For example with a compiler flag that then > stores this information in the executable (how?), or NVPTX_RUN_CC, and > GOMP_NVPTX_CC environment variables (or, *_SM?), respectively? I think it should be done with env vars if at all, because it can only be used to downgrade sm requirement within a generation, e.g. forcing sm_30 on a machine with a sm_35 accelerator. Alexander
