I've wondered about that as well.. I've seen a couple of places where this could be useful, but not nearly as many as in lldb. I'll let you be the judge of that.
On 2 June 2017 at 15:43, Zachary Turner <ztur...@google.com> wrote: > I wonder if this should go in LLVM? > > On Fri, Jun 2, 2017 at 7:35 AM Pavel Labath via Phabricator > <revi...@reviews.llvm.org> wrote: >> >> labath created this revision. >> Herald added subscribers: mgorny, emaste. >> >> It is intended to wrap functions which can fail with EINTR (which we >> have a surprising number of). It is inspired by the TEMP_FAILURE_RETRY >> macro in glibc, but I've c++-ified it and made it more generic (by >> specifying an explicit fail value), so it can also be used for functions >> like fopen(3). >> >> >> https://reviews.llvm.org/D33831 >> >> Files: >> include/lldb/Host/Host.h >> include/lldb/Utility/Status.h >> source/Host/common/File.cpp >> source/Host/macosx/Host.mm >> source/Host/posix/ConnectionFileDescriptorPosix.cpp >> source/Plugins/Process/FreeBSD/ProcessMonitor.cpp >> source/Plugins/Process/Linux/NativeProcessLinux.cpp >> source/Plugins/Process/NetBSD/NativeProcessNetBSD.cpp >> unittests/Host/CMakeLists.txt >> unittests/Host/HostTest.cpp >> > _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
