[Bug libgomp/111024] libgomp: FAILs with oldish libnuma/libmemkind

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:8f3c4517b1fff965f2bdedcf376dcfd91cda422b

commit r14-3287-g8f3c4517b1fff965f2bdedcf376dcfd91cda422b
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Aug 17 15:20:55 2023 +0200

    libgomp: call numa_available first when using libnuma

    The documentation requires that numa_available() is called and only
    when successful, other libnuma function may be called. Internally,
    it does a syscall to get_mempolicy with flag=0 (which would return
    the default policy if mode were not NULL). If this returns -1 (and
    not 0) and errno == ENOSYS, the Linux kernel does not have the
    get_mempolicy syscall function; if so, numa_available() returns -1
    (otherwise: 0).

    libgomp/

            PR libgomp/111024
            * allocator.c (gomp_init_libnuma): Call numa_available; if
            not available or not returning 0, disable libnuma usage.