similar to: [LLVMdev] Remaining Compiler-RT failures in ARM

On 10 October 2014 12:48, Renato Golin <renato.golin at linaro.org> wrote: > 0x0014b494 <+192>: andeq r1, r0, r4, asr #23 > 0x0014b498 <+196>: andseq r8, r2, r12, lsl #24 > 0x0014b49c <+200>: andeq r1, r0, r12, ror r7 > 0x0014b4a0 <+204>: ; <UNDEFINED> instruction: 0x00128bd0 > => 0x0014b4a4 <+208>: ;

Hi Evgeniy, So, to XFAIL some UBSAN failues, I found an issue: UndefinedBehaviorSanitizer-AddressSanitizer :: TestCases/TypeCheck/vptr.cpp UndefinedBehaviorSanitizer-Standalone :: TestCases/Misc/missing_return.cpp These two tests fail on that configuration, but pass when reversed. So, if I XFAIL: armv7l..., I get the following error: UndefinedBehaviorSanitizer-AddressSanitizer ::

Hi Everyone, When I used llvm-objdump to disassemble an ELF armv7 or thumb I have this error message: llvm-objdump: warning: invalid instruction encoding This message appears directly into the output and the output is mostly wrong (the invalid instruction create a shift in the addresses) : 1a6d: ff 2f e1 08 stmeq r1!, {r0, r1, r2, r3, r4, r5, r6, r7, r8, r9, r10, r11, sp} ^ 1a71: 30

Bill, For some reason the llvm-symbolizer tests fail on ppc: http://lab.llvm.org:8011/builders/clang-ppc64le-linux/builds/182/steps/ninja%20check%201/logs/stdio because it can't be started: /home/buildbots/ppc64le-clang-test/clang-ppc64le/stage1/./bin/llvm-symbolizer: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by

The standard objdump does not recognised the format. It works if I used an arm-linux-androideabi-objdump from the Android ndk but I am using the clang API to read binary inside my soft. This is why I was only working with llvm-objdump. > On 19 Jun 2016, at 15:03, Bruce Hoult <bruce at hoult.org> wrote: > > What happens if you use the standard bunutils objdump e.g. from macports

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom

On 10 October 2014 15:30, Evgeniy Stepanov <eugenis at google.com> wrote: > Could this be some kind of linker-generated compatibility magic? I'm not sure. Searching for "____asan_handle_no_return_veneer" on Google gets me this thread. :) I'm tempted to disable that test on ARM+Linux, since we use EHABI instead of SjLj... At least for now... --renato

Hi, I'm not sure what's up with BuiltinLongJmpTest. I think Greg was the last to do anything about arm-linux support in asan. As for the aarch64 failures, do you want to build the aarch64 bit stuff, but not run the tests? In cmake we try to detect target platforms supported by the compiler, but we don't check that binaries actuall run. But why is there so little failures, if the

Hi Evgeniy, I just created a new buildbot that compiles and tests compiler-rt together with LLVM/Clang using the CMake build: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/0 There are a few ASan failures and I'd like to check with you which of them are real failures that we need to fix and which are just unsupported / noise. These tests are running on an ARMv7

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom

Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

Kostya, Christophe, I'm running the full tests on AARch64 and the only RT test that fails is: UndefinedBehaviorSanitizer-Standalone :: TestCases/Float/cast-overflow.cpp The problem seems to be a trap in __sanitizer::internal_memchr() while trying to handle __ubsan::__ubsan_handle_float_cast_overflow(). I haven't looked at it in detail, has anyone seen this? Is UBSan meant to run on

Hello everyone, 9.0.0-rc5 was just tagged from the release_90 branch at r371837. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc5. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc5 Binaries will be added as they become available. There is only a single change from rc4 to rc5. Once more, the hope is that this will be the last release candidate and that we can

Hello again, 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they become available. There are not a lot of changes from rc3 to rc4, and there are again no open release blockers, so I'm hoping this will be the last

Hi All, I am first time trying build CLANG+LLVM using cmake+ninja build system. I updated all my CLANG+LLVM sources to current trunk, and I successfully built it using classic *make* build system. But, trying to build the same with cmake+ninja build system resulting in following build failures for compiler-rt sources. Am I missing something basics here? ==================== cmake command used:

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is

I'm seeing this too. CC'ing the author ubsan stuff. Richard, I know you were OK with only supporting Clang-bootstraps, but I don't think that's terribly viable here. We should be able to build ubsan's runtime with standards conforming code unless there is some fairly extreme reason not to... On Fri, Oct 12, 2012 at 7:19 AM, Mahesha HS <mahesha.llvm at gmail.com> wrote:

I use latest cmake+ninja which are built from latest sources. ================================= > cmake --version cmake version 2.8.9.20121011-g2876 ================================= -- mahesha On Fri, Oct 12, 2012 at 7:35 PM, Mahesha HS <mahesha.llvm at gmail.com> wrote: > Hi All, > > I am first time trying build CLANG+LLVM using cmake+ninja build > system. I updated all