Displaying 5 results from an estimated 5 matches for "gcc_eh".
Did you mean:
lgcc_eh
2014 Oct 22
3
[LLVMdev] LibUnwind into Compiler-RT?
...s hard and clumsy, not impossible.
Basically, I want to avoid requiring people to link against
libunwind+rt+libcxxabi if all they need is libcxx or rt.
>> An alternative to fix the libc++ tests on ARM would be to require
>> Compiler-RT to be there as well, but, as I said, Clang links gcc_eh
>> and gcc_s when you choose --rtlib=compiler-rt, making the exercise
>> moot.
> Clang's code isn't frozen... ;)
I know, I put it there. :)
I did it because that was what libgcc required, and I didn't want to
make compiler-RT depend on libc++, at least not at a Clang le...
2014 Oct 22
3
[LLVMdev] LibUnwind into Compiler-RT?
So, I remember we discussed this earlier this year, but I can't find the thread.
The idea is to move libunwind into compiler-rt for the simple reasons below:
1. Unwinding is not exclusive to C++, nor exception handling.
2. Clang still includes libgcc_s and libgcc_eh when using compiler-rt
(maybe eh isn't needed, but it was there for libgcc).
3. Testing the libunwind with libc++ on ARM is not possible, because
libgcc_s merges RT abi with unwind, duplicating the implementation of
some, but not all, unwind functions.
I'm not sure how the move would take...
2015 Aug 25
4
GPL Software
Le 25/08/2015 20:39, Renato Golin a écrit :
> I'm also interested in knowing what you did. I think most people here
> would be glad to know your peril and how you solved it.
Stack layout:
C++ code calls
|
|
JITted C code, compiled and linked on the fly tha calls
|
|
C++ code that throws
The throw must pass through the JITted code to arrive at the catch at
the top.
2014 Oct 22
2
[LLVMdev] LibUnwind into Compiler-RT?
...sed this earlier this year, but I can't find the
> thread.
> >
> > The idea is to move libunwind into compiler-rt for the simple reasons
> below:
> >
> > 1. Unwinding is not exclusive to C++, nor exception handling.
> > 2. Clang still includes libgcc_s and libgcc_eh when using compiler-rt
> > (maybe eh isn't needed, but it was there for libgcc).
> > 3. Testing the libunwind with libc++ on ARM is not possible, because
> > libgcc_s merges RT abi with unwind, duplicating the implementation of
> > some, but not all, unwind functions.
&g...
2016 Jul 21
3
[RFC] One or many git repositories?
> Which projects do we put under this monolithic repository?
The proposal at the moment is to include
llvm, clang, clang-tools-extra, lld, polly, lldb, llgo, compiler-rt,
openmp, and parallel-libs.
This is the set {llvm} plus the transitive closure of "projects that
are version-locked to a project in the set", where the closure is
taken over the set of all active LLVM