diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2020-11-30 15:15:20 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2021-01-14 18:48:00 +0100 |
| commit | 6106dfb9f73a33c87108ad5b2dcd4842bdd7828e (patch) | |
| tree | e630592c2d1f65096bace48916a55b24d1665001 /libgo/go | |
| parent | 57a4f5e4eacfbbbd0ca5f1e3f946c27d63e2b533 (diff) | |
| download | gcc-6106dfb9f73a33c87108ad5b2dcd4842bdd7828e.zip gcc-6106dfb9f73a33c87108ad5b2dcd4842bdd7828e.tar.gz gcc-6106dfb9f73a33c87108ad5b2dcd4842bdd7828e.tar.bz2 | |
[nvptx libgomp plugin] Build only in supported configurations
As recently again discussed in <https://gcc.gnu.org/PR97436> "[nvptx] -m32
support", nvptx offloading other than for 64-bit host has never been
implemented, tested, supported. So we simply should buildn't the nvptx libgomp
plugin in this case.
This avoids build problems if, for example, in a (standard) bi-arch
x86_64-pc-linux-gnu '-m64'/'-m32' build, libcuda is available only in a 64-bit
variant but not in a 32-bit one, which, for example, is the case if you build
GCC against the CUDA toolkit's 'stubs/libcuda.so' (see
<https://stackoverflow.com/a/52784819>).
This amends PR65099 commit a92defdab79a1268f4b9dcf42b937e4002a4cf15 (r225560)
"[nvptx offloading] Only 64-bit configurations are currently supported" to
match the way we're doing this for the HSA/GCN plugins.
libgomp/
PR libgomp/65099
* plugin/configfrag.ac (PLUGIN_NVPTX): Restrict to supported
configurations.
* configure: Regenerate.
* plugin/plugin-nvptx.c (nvptx_get_num_devices): Remove 64-bit
check.
Diffstat (limited to 'libgo/go')
0 files changed, 0 insertions, 0 deletions