SuccessChanges

Summary

  1. [libomptarget][nfc] Move some source into common from nvptx (details)
  2. [Signal] Allow llvm clients to opt into one-shot SIGPIPE handling (details)
Commit 5a4a05d776d3adacad344b2b5e15cf594c906bce by jonathanchesterfield
[libomptarget][nfc] Move some source into common from nvptx
Summary:
[libomptarget][nfc] Move some source into common from nvptx
Moves some source that compiles cleanly under amdgcn into a common
subdirectory Includes some non-trivial files and some headers. Keeps the
cuda file extension.
The build systems for different architectures seem unlikely to have much
in common. The idea is therefore to set include paths such that files
under common/src compile as if they were under arch/src as the mechanism
for sharing. In particular, files under common/src need to be able to
include target_impl.h.
The corresponding -Icommon is left out in favour of explicit includes on
the basis that the it makes it clearer which files under common are used
by a given architecture.
Reviewers: jdoerfert, ABataev, grokos
Reviewed By: ABataev
Subscribers: jfb, mgorny, openmp-commits
Tags: #openmp
Differential Revision: https://reviews.llvm.org/D70328
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/state-queue.h
The file was addedopenmp/libomptarget/deviceRTLs/common/src/task.cu
The file was addedopenmp/libomptarget/deviceRTLs/common/debug.h
The file was addedopenmp/libomptarget/deviceRTLs/common/src/critical.cu
The file was addedopenmp/libomptarget/deviceRTLs/common/state-queue.h
The file was addedopenmp/libomptarget/deviceRTLs/common/src/cancel.cu
The file was addedopenmp/libomptarget/deviceRTLs/common/src/loop.cu
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/task.cu
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/debug.h
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/loop.cu
The file was modifiedopenmp/libomptarget/deviceRTLs/nvptx/src/support.cu
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/state-queuei.h
The file was modifiedopenmp/libomptarget/deviceRTLs/nvptx/src/omptarget-nvptx.h
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/critical.cu
The file was modifiedopenmp/libomptarget/deviceRTLs/nvptx/CMakeLists.txt
The file was removedopenmp/libomptarget/deviceRTLs/nvptx/src/cancel.cu
The file was addedopenmp/libomptarget/deviceRTLs/common/state-queuei.h
Commit 4624e83ce7b124545b55e45ba13f2d900ed65654 by Vedant Kumar
[Signal] Allow llvm clients to opt into one-shot SIGPIPE handling
Allow clients of the llvm library to opt-in to one-shot SIGPIPE
handling, instead of forcing them to undo llvm's SIGPIPE handler
registration (which is brittle).
The current behavior is preserved for all llvm-derived tools (except
lldb) by means of a default-`true` flag in the InitLLVM constructor.
This prevents "IO error" crashes in long-lived processes (lldb is the
motivating example) which both a) load llvm as a dynamic library and b)
*really* need to ignore SIGPIPE.
As llvm signal handlers can be installed when calling into libclang
(say, via RemoveFileOnSignal), thereby overriding a previous SIG_IGN for
SIGPIPE, there is no clean way to opt-out of "exit-on-SIGPIPE" in the
current model.
Differential Revision: https://reviews.llvm.org/D70277
The file was modifiedllvm/lib/Support/Unix/Signals.inc
The file was modifiedllvm/lib/Support/InitLLVM.cpp
The file was modifiedlldb/tools/driver/Driver.cpp
The file was modifiedllvm/include/llvm/Support/Signals.h
The file was modifiedllvm/include/llvm/Support/InitLLVM.h
The file was modifiedlldb/tools/lldb-server/lldb-server.cpp
The file was modifiedllvm/lib/Support/Windows/Signals.inc