Changes in Signals.inc

e6e61e9b - Revert "Reapply: Add an error message to the default SIGPIPE handler"

Fri, 18 Nov 2022 00:07:15 +0000

Revert "Reapply: Add an error message to the default SIGPIPE handler"This patch is spamming compiles with unhelpful and confusing messages.E.g. the Linux kernel uses "grep -q" in several places. It's meant toquit with a return code of zero when the first match is found. This cancause a SIGPIPE signal, but that's expected, and there's no way to turnthis error message off to avoid spurious error messages.UNIX03 apparently doesn't require printing an error message on SIGPIPE,but specifically when there's an error on the stdout stream in a normalprogram flow, e.g. when SIGPIPE trap is disabled.A separate patch is planned to address the specific case we care mostabout (involving llvm-nm).This reverts commit b89bcefa6202e310eb3167dd1c37f1807377ec8d.Link: https://github.com/llvm/llvm-project/issues/59037Link: https://github.com/ClangBuiltLinux/linux/issues/1651Differential Revision: https://reviews.llvm.org/D138244(cherry picked from commit 4787efa38066adb51e2c049499d25b3610c0877b) List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

b89bcefa - Reapply: Add an error message to the default SIGPIPE handler

Thu, 09 Jun 2022 18:52:29 +0000

Reapply: Add an error message to the default SIGPIPE handlerUNIX03 conformance requires utilities to flush stdout before exiting and raisean error if writing fails. Flushing already happens on a call to exitand thus automatically on a return from main. Write failure is thendetected by LLVM's default SIGPIPE handler. The handler already exits witha non-zero code, but conformance additionally requires an error message.First reapply attempt I hadn't noticed the test had changed, hopefully thisgoes better. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

4badd4d4 - Revert "Add an error message to the default SIGPIPE handler"

Thu, 09 Jun 2022 18:01:13 +0000

Revert "Add an error message to the default SIGPIPE handler"It broke PPC bots. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

51b557ad - Add an error message to the default SIGPIPE handler

Wed, 11 May 2022 08:52:10 +0000

Add an error message to the default SIGPIPE handlerUNIX03 conformance requires utilities to flush stdout before exiting and raisean error if writing fails. Flushing already happens on a call to exitand thus automatically on a return from main. Write failure is thendetected by LLVM's default SIGPIPE handler. The handler already exits witha non-zero code, but conformance additionally requires an error message. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

b1c7889f - [config] Remove RETSIGTYPE from config.h.cmake, NFC

Fri, 03 Jun 2022 23:21:42 +0000

[config] Remove RETSIGTYPE from config.h.cmake, NFCThis doesn't need to be configurable. It was hardcoded to void in allLLVM build systems. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

7b53a45e - Revert "Add an error message to the default SIGPIPE handler"

Thu, 12 May 2022 07:30:53 +0000

Revert "Add an error message to the default SIGPIPE handler"It broke a PPC bot, for not immediately obvious reasons. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

e845f899 - Add an error message to the default SIGPIPE handler

Wed, 11 May 2022 08:52:10 +0000

f15014ff - Revert "Rename llvm::array_lengthof into llvm::size to match std::size from C++17"

Wed, 26 Jan 2022 15:55:53 +0000

Revert "Rename llvm::array_lengthof into llvm::size to match std::size from C++17"This reverts commit ef8206320769ad31422a803a0d6de6077fd231d2.- It conflicts with the existing llvm::size in STLExtras, which will now never be called.- Calling it without llvm:: breaks C++17 compat List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

ef820632 - Rename llvm::array_lengthof into llvm::size to match std::size from C++17

Wed, 26 Jan 2022 15:11:12 +0000

Rename llvm::array_lengthof into llvm::size to match std::size from C++17As a conquence move llvm::array_lengthof from STLExtras.h toSTLForwardCompat.h (which is included by STLExtras.h so no buildbreakage expected). List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

b81244fa - Add LLVM_ATTRIBUTE_USED to fix problems which could be exposed by aggressive global pointer variable removal

Mon, 26 Apr 2021 20:31:37 +0000

Add LLVM_ATTRIBUTE_USED to fix problems which could be exposed by aggressive global pointer variable removalNote to BuryPointer.cpp:GraveYard. 'unused' cannot prevent (1) dead storeelimination and (2) removal of the global pointer variable (D69428) but 'used' can.Discovered when comparing link maps between HEAD+D69428 and HEAD.Reviewed By: lattnerDifferential Revision: https://reviews.llvm.org/D101217 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

bf401256 - [Signal] Re-raise SIGPIPE if the handler is uninstalled

Fri, 08 Jan 2021 19:12:08 +0000

[Signal] Re-raise SIGPIPE if the handler is uninstalledInstead of falling through to RunSignalHandlers after the SIGPIPEhandler is uninstalled and we get a SIGPIPE, re-raise the signal, justlike we do for other IntSigs.This was discussed and informally OK'd here:https://reviews.llvm.org/rG9a3f892d018238dce5181e458905311db8e682f5#856804 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

960535d6 - Hint how to get a symbolized stack trace if llvm-symbolizer is not found on crashes

Fri, 25 Sep 2020 01:50:40 +0000

Hint how to get a symbolized stack trace if llvm-symbolizer is not found on crashesMost users of LLVM tools hit the raw traces and don't know how to get LLVM tosymbolize automatically for them.When we print the non-symbolized stack trace, we will add information abouthow to get it symbolized.Reviewed By: MaskRayDifferential Revision: https://reviews.llvm.org/D88269 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

f5314d15 - [Support] On Unix, let the CrashRecoveryContext return the signal code

Thu, 24 Sep 2020 12:14:45 +0000

[Support] On Unix, let the CrashRecoveryContext return the signal codeBefore this patch, the CrashRecoveryContext was returning -2 upon a signal, like ExecuteAndWait does. This didn't match the behavior on Windows, where the the exception code was returned.We now return the signal's code, which optionally allows for re-throwing the signal later. Doing so requires all custom handlers to be removed first, through llvm::sys::unregisterHandlers() which we made a public API.This is part of https://reviews.llvm.org/D70378 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

ed07e1fe - [SystemZ/ZOS] Add header file to encapsulate use of

Wed, 20 May 2020 09:10:31 +0000

[SystemZ/ZOS] Add header file to encapsulate use of The non-standard header file `` provides some return values.`EX_IOERR` is used to as a special value to signal a broken pipe to the clang driver.On z/OS Unix System Services, this header file does not exists. This patch- adds a check for ``, removing the dependency on `LLVM_ON_UNIX`- adds a new header file `llvm/Support/ExitCodes`, which either includes `` or defines `EX_IOERR`- updates the users of `EX_IOERR` to include the new header fileReviewed By: hubert.reinterpretcastDifferential Revision: https://reviews.llvm.org/D83472 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

a7da7e42 - [Support] Allow printing the stack trace only for a given depth

Wed, 26 Aug 2020 13:21:34 +0000

[Support] Allow printing the stack trace only for a given depthDifferential Revision: https://reviews.llvm.org/D85458 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

60434989 - Use llvm::is_contained where appropriate (NFC)

Sun, 02 Aug 2020 04:49:38 +0000

Use llvm::is_contained where appropriate (NFC)Use llvm::is_contained where appropriate (NFC)Reviewed By: kazuDifferential Revision: https://reviews.llvm.org/D85083 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

a1f16998 - [Support] Optionally call signal handlers when a function wrapped by the the CrashRecoveryContext fails

Sat, 11 Jan 2020 20:27:07 +0000

[Support] Optionally call signal handlers when a function wrapped by the the CrashRecoveryContext failsThis patch allows for handling a failure inside a CrashRecoveryContext in the same way as the global exception/signal handler. A failure will have the same side-effect, such as cleanup of temporarty file, printing callstack, calling relevant signal handlers, and finally returning an exception code. This is an optional feature, disabled by default.This is a support patch for D69825.Differential Revision: https://reviews.llvm.org/D70568 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

9a3f892d - [Signal] Allow one-shot SIGPIPE handler to be reached

Thu, 05 Dec 2019 03:21:14 +0000

[Signal] Allow one-shot SIGPIPE handler to be reachedAs SIGPIPE is no longer in the IntSigs array, handle SIGPIPE beforehandling any interrupt signals.Thanks to Alexandre Ganea for pointing out the issue here. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

4624e83c - [Signal] Allow llvm clients to opt into one-shot SIGPIPE handling

Thu, 14 Nov 2019 22:30:56 +0000

[Signal] Allow llvm clients to opt into one-shot SIGPIPE handlingAllow clients of the llvm library to opt-in to one-shot SIGPIPEhandling, instead of forcing them to undo llvm's SIGPIPE handlerregistration (which is brittle).The current behavior is preserved for all llvm-derived tools (exceptlldb) by means of a default-`true` flag in the InitLLVM constructor.This prevents "IO error" crashes in long-lived processes (lldb is themotivating 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 forSIGPIPE, there is no clean way to opt-out of "exit-on-SIGPIPE" in thecurrent model.Differential Revision: https://reviews.llvm.org/D70277 List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc

d0bd3fc8 - Revert "Disable exit-on-SIGPIPE in lldb"

Thu, 24 Oct 2019 19:08:24 +0000

Revert "Disable exit-on-SIGPIPE in lldb"This reverts commit 32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30.In post-commit review, Pavel pointed out that there's a simpler way toignore SIGPIPE in lldb that doesn't rely on llvm's handlers. List of files: /llvm-project-15.0.7/llvm/lib/Support/Unix/Signals.inc