<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/llvm/lib/Support/Unix, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2020-01-11T20:27:07+00:00</updated>
<entry>
<title>[Support] Optionally call signal handlers when a function wrapped by the the CrashRecoveryContext fails</title>
<updated>2020-01-11T20:27:07+00:00</updated>
<author>
<name>Alexandre Ganea</name>
<email>alexandre.ganea@ubisoft.com</email>
</author>
<published>2020-01-11T20:27:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a1f16998f371870ca4da8b3c00a093c607a36ddd'/>
<id>urn:sha1:a1f16998f371870ca4da8b3c00a093c607a36ddd</id>
<content type='text'>
This 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
</content>
</entry>
<entry>
<title>[Support][NFC] Make some helper functions "static" in Memory.inc</title>
<updated>2020-01-09T17:46:21+00:00</updated>
<author>
<name>Bruno Ricci</name>
<email>riccibrun@gmail.com</email>
</author>
<published>2020-01-09T17:38:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2fe45e029ddfa65880cfe5c3501db12a81cdcbd2'/>
<id>urn:sha1:2fe45e029ddfa65880cfe5c3501db12a81cdcbd2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[Signal] Allow one-shot SIGPIPE handler to be reached</title>
<updated>2019-12-05T03:38:19+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2019-12-05T03:21:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9a3f892d018238dce5181e458905311db8e682f5'/>
<id>urn:sha1:9a3f892d018238dce5181e458905311db8e682f5</id>
<content type='text'>
As SIGPIPE is no longer in the IntSigs array, handle SIGPIPE before
handling any interrupt signals.

Thanks to Alexandre Ganea for pointing out the issue here.
</content>
</entry>
<entry>
<title>[Signal] Allow llvm clients to opt into one-shot SIGPIPE handling</title>
<updated>2019-11-18T18:27:27+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2019-11-14T22:30:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4624e83ce7b124545b55e45ba13f2d900ed65654'/>
<id>urn:sha1:4624e83ce7b124545b55e45ba13f2d900ed65654</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Avoid duplicate exe_path definition on recent FreeBSD</title>
<updated>2019-11-18T13:51:22+00:00</updated>
<author>
<name>Ed Maste</name>
<email>emaste@freebsd.org</email>
</author>
<published>2019-11-18T13:49:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b462cdff05b82071190e8bfd1078a2c76933b19b'/>
<id>urn:sha1:b462cdff05b82071190e8bfd1078a2c76933b19b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>On FreeBSD use AT_EXECPATH from ELF auxiliary vectors for getExecutablePath</title>
<updated>2019-11-14T14:48:48+00:00</updated>
<author>
<name>Ed Maste</name>
<email>emaste@freebsd.org</email>
</author>
<published>2019-11-13T18:24:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a0a38b81ea911f1cd4e400f1ab54dd4930598a7c'/>
<id>urn:sha1:a0a38b81ea911f1cd4e400f1ab54dd4930598a7c</id>
<content type='text'>
/proc/curproc/file and the KERN_PROC_PATHNAME sysctl may not return the
desired path if there are multiple hardlinks to the file, or if the path has
expired from the namecache.

Reviewed By:	theraven

Differential Revision:	https://reviews.llvm.org/D70198
</content>
</entry>
<entry>
<title>[Support] Use /proc/self/exe for GNU Hurd</title>
<updated>2019-11-01T17:27:27+00:00</updated>
<author>
<name>kristina</name>
<email>notstina@gmail.com</email>
</author>
<published>2019-11-01T17:27:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f42671239ffd414c3056be9a04d8678860800148'/>
<id>urn:sha1:f42671239ffd414c3056be9a04d8678860800148</id>
<content type='text'>
Use `/proc/self/exe` to get the current executable
path on GNU Hurd.

Patch by sthibaul (Samuel Thibault)

Differential Revision: https://reviews.llvm.org/D69683
</content>
</entry>
<entry>
<title>Revert "Disable exit-on-SIGPIPE in lldb"</title>
<updated>2019-10-24T20:19:49+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2019-10-24T19:08:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=d0bd3fc88be54c4e11f49cfa31e427700bb1e9af'/>
<id>urn:sha1:d0bd3fc88be54c4e11f49cfa31e427700bb1e9af</id>
<content type='text'>
This reverts commit 32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30.

In post-commit review, Pavel pointed out that there's a simpler way to
ignore SIGPIPE in lldb that doesn't rely on llvm's handlers.
</content>
</entry>
<entry>
<title>Reland "[Support] Add a way to run a function on a detached thread""</title>
<updated>2019-10-23T13:51:44+00:00</updated>
<author>
<name>Sam McCall</name>
<email>sammccall@google.com</email>
</author>
<published>2019-10-23T13:34:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a9c3c176ad741b9c2b915abc59dd977d0299c53f'/>
<id>urn:sha1:a9c3c176ad741b9c2b915abc59dd977d0299c53f</id>
<content type='text'>
This reverts commit 7bc7fe6b789d25d48d6dc71d533a411e9e981237.
The immediate callers have been fixed to pass nullopt where appropriate.
</content>
</entry>
<entry>
<title>Revert "[Support] Add a way to run a function on a detached thread"</title>
<updated>2019-10-23T13:10:35+00:00</updated>
<author>
<name>Sam McCall</name>
<email>sammccall@google.com</email>
</author>
<published>2019-10-23T13:10:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=7bc7fe6b789d25d48d6dc71d533a411e9e981237'/>
<id>urn:sha1:7bc7fe6b789d25d48d6dc71d533a411e9e981237</id>
<content type='text'>
This reverts commit 40668abca4d307e02b33345cfdb7271549ff48d0.
This causes clang tests to fail, as stacksize=0 is being explicitly passed and
is no longer a no-op.
</content>
</entry>
</feed>
