[Bug libgomp/65099] nvptx offloading: hard-coded 64-bit assumptions

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65099

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Thomas Schwinge
<tschwinge@gcc.gnu.org>:

https://gcc.gnu.org/g:0f1e1069a753e912b058f0d4bf599f0edde28408

commit r9-9182-g0f1e1069a753e912b058f0d4bf599f0edde28408
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Mon Nov 30 15:15:20 2020 +0100

    [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.

    (cherry picked from commit 6106dfb9f73a33c87108ad5b2dcd4842bdd7828e)