LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 49250 - current libomptarget test failures on x86-64 Linux
Summary: current libomptarget test failures on x86-64 Linux
Status: RESOLVED FIXED
Alias: None
Product: OpenMP
Classification: Unclassified
Component: Runtime Library (show other bugs)
Version: unspecified
Hardware: PC Linux
: P normal
Assignee: Unassigned LLVM Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-18 10:37 PST by Joel E. Denny
Modified: 2021-09-27 10:25 PDT (History)
4 users (show)

See Also:
Fixed By Commit(s):


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joel E. Denny 2021-02-18 10:37:03 PST
I see 4 consistent libomptarget test failures on main at 3c4c205060c.

I am running Ubuntu 18.04.5 LTS on x86_64 with an NVIDIA GPU.  I am building with -DLLVM_ENABLE_PROJECTS=clang and -DLLVM_ENABLE_RUNTIMES=openmp.  Compiler is clang 10 (for building clang and llvm).  CUDA is 11.2.

Below are some relevant excerpts from lit's output.  Please let me know if you need more information.  It's possible some of this is just my configuration, so let me know if you cannot reproduce.

```
Failed Tests (4):
  libomptarget :: mapping/lambda_mapping.cpp
  libomptarget :: offloading/bug49021.cpp
  libomptarget :: offloading/memory_manager.cpp
  libomptarget :: offloading/parallel_offloading_map.cpp


FAIL: libomptarget :: offloading/memory_manager.cpp

$ ":" "RUN: at line 4"

memory_manager.cpp.tmp-x86_64-pc-linux-gnu: /home/jdenny/ornl/llvm/llvm-mono-git/openmp/libomptarget/test/offloading/memory_manager.cpp:37: int main(int, char **): Assertion `buffer[j] == i' failed.


FAIL: libomptarget :: offloading/parallel_offloading_map.cpp

$ ":" "RUN: at line 4"

parallel_offloading_map.cpp.tmp-x86_64-pc-linux-gnu: /home/jdenny/ornl/llvm/llvm-mono-git/openmp/libomptarget/test/offloading/parallel_offloading_map.cpp:35: int main(int, char **): Assertion `array[i] == ref' failed.


FAIL: libomptarget :: mapping/lambda_mapping.cpp

$ ":" "RUN: at line 5"

ptxas /tmp/lambda_mapping-081ea9.s, line 828; error   : Not a name of any known instruction: 'activemask'
ptxas fatal   : Ptx assembly aborted due to errors
clang-13: error: ptxas command failed with exit code 255 (use -v to see invocation)


FAIL: libomptarget :: offloading/bug49021.cpp

$ ":" "RUN: at line 5"

ptxas /tmp/bug49021-57542e.s, line 482; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 1032; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 1361; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 1379; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 1391; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 1987; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 2608; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 2937; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 2956; error   : Not a name of any known instruction: 'activemask'
ptxas /tmp/bug49021-57542e.s, line 2968; error   : Not a name of any known instruction: 'activemask'
ptxas fatal   : Ptx assembly aborted due to errors
clang-13: error: ptxas command failed with exit code 255 (use -v to see invocation)
````

Johannes: These are 4 of the test failures we discussed on Monday.  The 5th stopped failing after another pull.
Comment 1 Joel E. Denny 2021-02-18 16:06:17 PST
I looked into the ptxas failure.  Because of my PATH, it actually picked up ptxas for CUDA 9.1, but there's a recent cmake change that's converting 91 to 9100 instead of 9010, so code is being compiled incorrectly.  I'm working on a cmake fix.
Comment 2 Joel E. Denny 2021-02-18 17:20:49 PST
D97012 addresses the ptxas failures.
Comment 3 Luke 2021-02-25 09:45:04 PST
On openSUSE Tumbleweed I see Failed Tests (2):
libomptarget :: offloading/memory_manager.cpp
libomptarget :: offloading/parallel_offloading_map.cpp

With the exact same Assertion failures as Joel. 


The same system passes these tests under Ubuntu 20.4. Shilei suggested this could be related to Bug 48330 or elf64 using libffi. Hope this info helps.
Comment 4 Luke 2021-05-01 09:55:08 PDT
libomptarget :: offloading/memory_manager.cpp - Bug 49532 
libomptarget :: offloading/parallel_offloading_map.cpp - Bug 49533
Comment 5 Luke 2021-09-27 10:25:28 PDT
The parallel_offloading_map.cpp, memory_manager.cpp, and offloading/bug49021.cpp tests were disabled for x86_64-pc-linux-gnu:
https://github.com/llvm/llvm-project/commit/ad0f6e1d984067a3dc81c17abcdd2fc3c7ff9946

mapping/lambda_mapping.cpp with:
https://github.com/llvm/llvm-project/commit/ef8b3b5ffd562955fbb78c72c7820cd9cd99d313