Page MenuHomeFreeBSD

llvm: Support: don't block signals around close if it can be avoided
ClosedPublic

Authored by mjg on Dec 9 2023, 7:49 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 26, 5:29 AM
Unknown Object (File)
Mar 13 2024, 3:37 AM
Unknown Object (File)
Jan 10 2024, 7:53 AM
Unknown Object (File)
Jan 7 2024, 8:30 PM
Unknown Object (File)
Dec 30 2023, 5:41 AM
Unknown Object (File)
Dec 29 2023, 6:51 PM
Unknown Object (File)
Dec 27 2023, 2:40 AM

Details

Summary

Upstream is giving radio silence, see https://github.com/llvm/llvm-project/pull/73009

There is tons of other perf breakage which I may get around to.

llvm: Support: don't block signals around close if it can be avoided

Signal blocking originally showed up in 51c2afc4b65b2782 ("Support:
Don't call close again if we get EINTR"), but it was overzealous --
there are systems where the error is known to be fine.

This commit elides signal blocking for said systems (the list is
incomplete though).

Note close() can still fail for other reasons (like ENOSPC), in which
case an error will be returned while the fd slot is cleared up.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable