On 12/19/2017 04:39 PM, Tom de Vries wrote: > On 12/20/2017 12:25 AM, Cesar Philippidis wrote: >> In CUDA 9, Nvidia removed support for treating the labels of functions >> as generic address spaces as part of their PTX 6.0 changes. More >> specifically, >> <http://docs.nvidia.com/cuda/parallel-thread-execution/index.html#changes-in-ptx-isa-version-6-0>: >> >> >> Support for taking address of labels, using labels in initializers >> which was unimplemented has been removed from the spec. >> >> Despite targeting PTX 3.0, the ptxas assembler shipped with CUDA 9 no >> longer support that legacy functionality. Consequently, this prevented >> newlib from building. This patch fixes that problem by not using a >> generic address space when initializing variables using a label address. >> > > What is the effect for pre-9.0 cudas?
No change in the libgomp execution test suite as an accelerator. >> Is this OK for trunk? >> > > How did you test this? Just libgomp as an accelerator for now. I'm trying to get standalone nvptx working right now. Which testsuites do you usually run? I only see the test results for check-gcc-c in your nightly build bot. By the way, do you know what caused the recent nvptx breakage in trunk? Cesar