Author: ddunbar
Date: Thu Jan 3 15:24:50 2019
New Revision: 350372
URL: http://llvm.org/viewvc/llvm-project?rev=350372&view=rev
Log:
Adopt SwiftABIInfo for WebAssembly.
Summary:
- This adopts SwiftABIInfo as the base class for WebAssemblyABIInfo, which is
in keeping with what is done for other
IIRC, and I can hardly guarantee I do, the issue is that libclang
installing signal handlers doesn’t play well with the arbitrary
applications which can be linking libclang.
- Daniel
On Thu, Nov 16, 2017 at 3:26 PM Rafael Avila de Espindola <
rafael.espind...@gmail.com> wrote:
> Daniel Dunbar
ddunbar added a comment.
I am too out of the loop on Clang development to be able to comment on the
specific direction, but I will just say that I am highly in favor of adding new
features in this direction. Thank you!
https://reviews.llvm.org/D24933
The original motivation for organizing things this way was to try and
always be in the situation where, when linking against the latest
deployment target, we should never need the extra library (because the
content will be present in libSystem). This is useful in helping to ensure
we don't unnecess
I believe you are thinking of: http://reviews.llvm.org/D18185
On Tue, May 31, 2016 at 2:32 PM, Paul Robinson
wrote:
> probinson added a subscriber: probinson.
> probinson added a comment.
>
> Do I remember that somebody was working on a more generic expression-like
> syntax for REQUIRES? If th
I agree with Chandler the default should be no names for -Asserts builds.
What I wanted originally was that the stripping of names be a runtime
choice (since the performance overhead of it was minimal when I measured
it), so that when we need to debug with a production compiler, it would
still be