search for: armv8l

There’s this bug: https://bugs.llvm.org/show_bug.cgi?id=38468. I’ve managed to track it down to a configuration issue. The thing is that in order for libunwind to be usable on ARM Linux, it should be built with the -funwind-tables flag. This flag is conditionally set here: https://github.com/llvm/llvm-project/blob/master/libunwind/CMakeLists.txt#L294, if the compiler “supports” it. However, the

...roblem if an > exception were being propagated through a libunwind function, and that > shouldn't happen unless something has gone badly wrong. Can you explain what you mean? > I tried the > example with the armv7l release of clang 8.0 which I happened to have > installed on an Armv8l machine and the program worked. I was able to > reproduce the problem with the PR with the default Ubuntu16.04 clang > (3.8) and libc++-dev package. > > I also note that when looking at the link line for the example in the > PR, clang was linking libgcc_s and not libunwind so I thin...

...ase then yes we would need unwinding > information. We'd also need unwinding information in libunwind if it > called a function that could throw an exception. > >> I tried the >> example with the armv7l release of clang 8.0 which I happened to have >> installed on an Armv8l machine and the program worked. I was able to >> reproduce the problem with the PR with the default Ubuntu16.04 clang >> (3.8) and libc++-dev package. >> >> I also note that when looking at the link line for the example in the >> PR, clang was linking libgcc_s and not...

...we would need unwinding >> information. We'd also need unwinding information in libunwind if it >> called a function that could throw an exception. >> >> I tried the >> example with the armv7l release of clang 8.0 which I happened to have >> installed on an Armv8l machine and the program worked. I was able to >> reproduce the problem with the PR with the default Ubuntu16.04 clang >> (3.8) and libc++-dev package. >> >> I also note that when looking at the link line for the example in the >> PR, clang was linking libgcc_s and not...