search for: gaborb

Hi Tim, I just read this thread and I see that you mentioned the buildbot and my name. > - LLVM test suite enabled in the buildbot and testing ARM64 (Gabor) What exactly I can do to help you with the merge process? Best regards, Gabor Ballabas -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Gabor, It seems the linker is playing tricks on the full bot: http://lab.llvm.org:8011/builders/clang-native-aarch64-full Sometimes it works by cleaning the stage2 dir completely, but there may be some extra bits that we're not considering. However, I can't see why any of the commits on the first failure did anything to the relocations on AArhc64... cheers, --renato

Hi, I've got the same 4 unexpected passing tests on the AArch64 buildbot. I checked the buildbot logs and before these tests started to fail all MCJIT tests were unsupported. I think that maybe this commit - http://llvm.org/viewvc/llvm-project?revision=193459&view=revision <http://llvm.org/viewvc/llvm-project?revision=193459&view=revision> caused the issue but I'm still

Hi Gabor, I noticed that one particular test fails intermittently on the AArch64 bot: http://lab.llvm.org:8011/builders/clang-native-aarch64-full FAIL: Profile:: instrprof-set-filename-then-reset-default.c Some times on stage1, others on stage2, others no fail at all. All the commits during these builds are not related to profiling or AArch64, so I believe this has something to do with the

Hi, Testing llvm trunk on openSUSE 13.1 ARMv7 I got 4 unexpected passes: Unexpected Passing Tests (4): LLVM :: ExecutionEngine/MCJIT/cross-module-sm-pic-a.ll LLVM :: ExecutionEngine/MCJIT/multi-module-sm-pic-a.ll LLVM :: ExecutionEngine/MCJIT/remote/cross-module-sm-pic-a.ll LLVM :: ExecutionEngine/MCJIT/remote/multi-module-sm-pic-a.ll And one FAIL: Failing Tests (1): LLVM ::

Hi Evgeny, I know of the current machine outliner in LLVM. If you look in the "More detailed performance data" in the end section it includes performance comparisons to the machine outliner. As for the algorithmic approach they are kind of similar. Machine Outliner: - Builds a suffix tree based on identical equivalence between machine instrs. - Uses target specific cost model for

Dear LLVM developers, My name is Gabor Ballabas. I work for the University of Szeged (Hungary) and we have an ongoing project with the goal of setting up and maintaining an LLVM buildbot for the ARMv8 - alias Aarch64 - architecture. Due to lack of existing hardware for this architecture we use ARM's Foundation Model to run the Aarch64 binaries. (See: