Skip to content

PR for llvm/llvm-project#59037 #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 23, 2022
Merged

PR for llvm/llvm-project#59037 #217

merged 2 commits into from
Nov 23, 2022

Conversation

llvmbot
Copy link
Member

@llvmbot llvmbot commented Nov 18, 2022

tstellar and others added 2 commits November 15, 2022 22:28
This patch is spamming compiles with unhelpful and confusing messages.
E.g. the Linux kernel uses "grep -q" in several places. It's meant to
quit with a return code of zero when the first match is found. This can
cause a SIGPIPE signal, but that's expected, and there's no way to turn
this 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 normal
program flow, e.g. when SIGPIPE trap is disabled.

A separate patch is planned to address the specific case we care most
about (involving llvm-nm).

This reverts commit b89bcef.

Link: llvm/llvm-project#59037
Link: ClangBuiltLinux/linux#1651

Differential Revision: https://reviews.llvm.org/D138244

(cherry picked from commit 4787efa)
@llvmbot
Copy link
Member Author

llvmbot commented Nov 18, 2022

@kees @nickdesaulniers What do you think about merging this PR to the release branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tools should _not_ catch their own SIGPIPE
3 participants