diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2022-06-10 21:19:51 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2022-06-10 21:19:51 +0200 |
| commit | 1eff4872d2e57c481f7218d25eecbfba647504e1 (patch) | |
| tree | 0699e6796633c90c88a875acf8c489b3fbe72487 /gcc/tree-cfg.cc | |
| parent | c08ba00487c44c4e363f23bb1652f1d0cb6831c2 (diff) | |
| download | gcc-1eff4872d2e57c481f7218d25eecbfba647504e1.zip gcc-1eff4872d2e57c481f7218d25eecbfba647504e1.tar.gz gcc-1eff4872d2e57c481f7218d25eecbfba647504e1.tar.bz2 | |
openmp: Call dlopen with "libmemkind.so.0" rather than "libmemkind.so"
On Thu, Jun 09, 2022 at 12:11:28PM +0200, Thomas Schwinge wrote:
> > This patch adds support for dlopening libmemkind.so
>
> Instead of 'dlopen'ing literally 'libmemkind.so':
> ..., shouldn't this instead 'dlopen' 'libmemkind.so.0'? At least for
> Debian/Ubuntu, the latter ('libmemkind.so.0') is shipped in the "library"
> package:
I agree and I've actually noticed it too right before committing, but I thought
I'll investigate and tweak incrementally because "libmemkind.so"
is what I've actually tested (it is what llvm libomp uses).
Here is the now tested incremental fix.
2022-06-10 Jakub Jelinek <jakub@redhat.com>
* allocator.c (gomp_init_memkind): Call dlopen with "libmemkind.so.0"
rather than "libmemkind.so".
Diffstat (limited to 'gcc/tree-cfg.cc')
0 files changed, 0 insertions, 0 deletions