search for: __cxa_

...following the steps for a combination of multiple projects. Initially, it failed to build because it couldn't find llvm-project/libcxx-abi. I symlinked libcxxabi to libcxx-abi, deleted the build directory and tried again. It fails to build, but this time with a bunch of undefined references to __cxa_XXX symbols. I didn't investigate further. >>> >>> Should this have just worked out of the box? >> >> Yes, can you post your cmake invocation, I’ll investigate. > > Sorry, I should have done that initially. I copied it from the website: > > cmake -GN...

On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> > wrote: > > > > well, top-of-branch lldb uses this code, that's how I found it. Do you > mean libc++'s demangler? > > Thanks for explaining, this is the first time

Hello, Renato > If the tables are different, when you link code compiled with Clang and GCC, > both using the same personality routine (GCC's or Clang's, but not both), > how do you expect them to work together? Because both tables are "standard" ? > Nevertheless, I digress. I may have started it the wrong way, but my > immediate goal is to compile a simple

> -----Original Message----- > From: Anton Korobeynikov [mailto:anton at korobeynikov.info] > > Neither llvm-gcc nor clang support exceptions on ARM (except, maybe, > sjlj excheptions on arm/darwin). I have some patched uncommitted for > EH on ARM but they are too far from being complete. Hi Anton, Are you actively working in that area? I did some experiments and managed to

...Requirement: The choice of unwinder should only minimally affect the basic structure of the IR. At a gloss, the code should differ only in (1) the structure of the unwinder-specific data for unwind actions (see below) and (2) high-level behavioral differences, like the calls to __cxa_{begin,end}_catch required by the Itanium EH ABI. Languages can define a pretty wide range of different actions which might need to be performed when unwinding into a function, but I believe they can be categorized into two classes: - First, actions taken in response to the exception itself;...

...are also caused by the "exception_ptr not yet implemented" error, but a number of them fail with other assertions, probably due to failing tests. One of the omp test failures is also due to "exception_ptr not yet implemented", but the other one just fails to link, with lots of __cxa_* symbols missing. The libunwind tests all fail with "/usr/local/bin/ld: cannot find -lc++abi", probably because libc++abi was disabled, since it does not work on FreeBSD. Most of the lld and lldb tests also fail due to "exception_ptr not yet implemented". Last but not least,...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>