search for: aarch64

...y to compiled and run. more investigation and test and code modify need to be done ,but IMO this is a good beginning !! to compile R on windows 11 arm64 just need : 1 svn checkout R-trunk and add USE_LLVM=YES in MKRules.dist or Mkrules.local 2 install msys2 and clangarm64 package mingw-w64-clang-aarch64-brotli 1.0.9-6 mingw-w64-clang-aarch64-bzip2 1.0.8-2 mingw-w64-clang-aarch64-c-ares 1.19.1-1 mingw-w64-clang-aarch64-ca-certificates 20230311-1 mingw-w64-clang-aarch64-clang 16.0.5-3 mingw-w64-clang-aarch64-compiler-rt 16.0.5-3 mingw-w64-clang-aarch64-crt-git 11.0.0.r107.gd367cc9d7-1 mingw-w64-c...

Hi, I've seen this issue pop up on the mailing list a couple of times before with no resolution [1][2][3]. It has been getting really bad for our AArch64 buildbots lately. You can see a few examples at the end of my email [4], but we have the same failures on a couple of other bots as well. Does anyone have any idea how to reproduce / investigate these issues? If not, is it reasonable to mark the tests as unsupported on AArch64? Thanks, Diana [1]...

Hi, We are now about halfway between the 3.4 and 3.5 releases, and I would like to start preparing for a 3.4.1 release. Here is my proposed release schedule: Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch. April 9 - April 18: Testing Phase April 18: 3.4.1 Release How you can help: - If you have any bug fixes you think should be included to 3.4.1, send me an

...ome/rkotler/llvm_3_ 2/install/bin/clang++ You should run debug and retail builds too because the warnings can become serious if there is something used in a DEBUG that is only referenced there. llvm[3]: Compiling HexagonAsmPrinter.cpp for Debug+Asserts build /home/rkotler/llvm_trunk/lib/Target/AArch64/AArch64ISelLowering.cpp:4244:22: error: comparison of integers of different signs: 'int' and 'unsigned int' [-Werror,-Wsign-compare] assert((Lane < V1.getOperand(0).getValueType().getVectorNumElements()) ~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~...

Hi, I am trying to cross compile release-10.x to AArch64 (target=aarch64-linux-gnu), and the directions listed at [1] are not completing the initial cmake step. I'm currently running Manjaro, with the aarch64-linux-gnu package (and associated binutils, headers, and glibc packages). My cmake command is cmake -DCMAKE_CROSSCOMPILING=True -DCMAKE_INST...

...bin/clang++ > > > You should run debug and retail builds too because the warnings can become > serious if there is something used in a DEBUG that is only referenced there. > > llvm[3]: Compiling HexagonAsmPrinter.cpp for Debug+Asserts build > /home/rkotler/llvm_trunk/lib/Target/AArch64/AArch64ISelLowering.cpp:4244:22: > error: > comparison of integers of different signs: 'int' and 'unsigned int' > [-Werror,-Wsign-compare] > assert((Lane < > V1.getOperand(0).getValueType().getVectorNumElements()) > ~~~~ ^ &gt...

...; >> You should run debug and retail builds too because the warnings can become >> serious if there is something used in a DEBUG that is only referenced there. >> >> llvm[3]: Compiling HexagonAsmPrinter.cpp for Debug+Asserts build >> /home/rkotler/llvm_trunk/lib/Target/AArch64/AArch64ISelLowering.cpp:4244:22: >> error: >> comparison of integers of different signs: 'int' and 'unsigned int' >> [-Werror,-Wsign-compare] >> assert((Lane < >> V1.getOperand(0).getValueType().getVectorNumElements()) >>...

...that he might be > willing to do this) I am, yes. > - For others who want to help test, compiling and running your > codebases on QEMU (no crypto extensions) Some reasonable description of how this works would be awesome. > > - Feature parity - to the level found in the ARM64 and AArch64 backends today As a note this should definitely be "Today", as in the day you sent the email/had the meeting/etc. No new work should be considered part of the final sign off - basically a gentle chide for people to stop putting new features into the existing AArch64 backend :) -eric

Details of the changes in second patch set as outlined in the first mail of this series: -------------------------------------------------------------------------------------------------------------------------- diff --git a/usr/include/arch/aarch64/klibc/archconfig.h b/usr/include/arch/aarch64/klibc/archconfig.h index 5cc1e7e..5ee278d 100644 --- a/usr/include/arch/aarch64/klibc/archconfig.h +++ b/usr/include/arch/aarch64/klibc/archconfig.h @@ -11,5 +11,7 @@ /* Use rt_* signals */ #define _KLIBC_USE_RT_SIG 1 +#define _KLIBC_NO_MMU 0 +#defin...

...chset for the architecture as it > is not merged, with signed-offs by both of you guys. Yes, we can do that. Do you prefer a patch to the mailing list or a git repo from which you can pull? Anil's git repo is the combined set of patches. I made some initial changes to get klibc to build for Aarch64, Anil started from that position and fixed that code to actually get it working. > > usr/klibc/arch/aarch64/Kbuild > > usr/klibc/arch/aarch64/MCONFIG > > usr/klibc/arch/aarch64/crt0.S > > usr/klibc/arch/aarch64/link.c > > usr/klibc/arch/aarch64/mknod.c > > usr/...

...rst set of patches from Neil Williams fixes the build issues. The second set of patches from Anil Singhar fixes functionalities. The following files have changed in the second set of patches ------------------------------------------------------------------------------------------ usr/include/arch/aarch64/klibc/archconfig.h usr/include/arch/aarch64/klibc/archsetjmp.h usr/include/arch/aarch64/klibc/archstat.h usr/include/sys/stat.h usr/include/unistd.h usr/klibc/SYSCALLS.def usr/klibc/arch/aarch64/Kbuild usr/klibc/arch/aarch64/MCONFIG usr/klibc/arch/aarch64/crt0.S usr/klibc/arch/aarch64/link.c usr/kl...

Compiling for AArch64: CommandLine Error: Option 'aarch64-branch-relax' registered more than once! Hi all! I am trying to run LDC (LLVM-based D compiler) on AArch64. The compiler contains all IR and target specific passes. You can view it as combined llc/opt tool. It uses the same strategy as opt to collect...

Hi Adhemerval, Some UBSan tests are timing out randomly. http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full ex: http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/902 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/894 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/906 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/902 The time...

Hi, I wonder if this is a valid flag in either clang/gcc. The flag in question is "-march=aarch64". I verified with latest tip and neither clang nor gcc fail to recognize this flag. This piece of code is in cmake/config-ix.cmake in compiler-rt repo. + elseif("${COMPILER_RT_TEST_TARGET_ARCH}" MATCHES "aarch64") + test_target_arch(aarch64 "-march=aarch64")...

Attached is a working patch set for llvm to be able to emit arm64 (currently as triple aarch64-apple-ios) mach-o object files, in case someone is interested. I'm not sure if the llvm maintainers want the patch given the previous message that there's going to be an official patch set from apple to support this, but here is mine. What works (tested on an iPhone 5S): * objc strings,...

...e come up with a single patchset for the architecture as it is not merged, with signed-offs by both of you guys. > The following files have changed in the second set of patches > ------------------------------------------------------------------------------------------ > usr/include/arch/aarch64/klibc/archconfig.h > usr/include/arch/aarch64/klibc/archsetjmp.h > usr/include/arch/aarch64/klibc/archstat.h > usr/include/sys/stat.h > usr/include/unistd.h > usr/klibc/SYSCALLS.def ok fine. > usr/klibc/arch/aarch64/Kbuild > usr/klibc/arch/aarch64/MCONFIG > usr/klibc/arch/a...

On 5 May 2016 at 13:01, Bradley Smith <Bradley.Smith at arm.com> wrote: > Allowing -march=aarch64/arm64 is somewhat misleading I think, -march is used > for specifying an architecture version to target whereas aarch64/arm64 don’t > convey any information to that effect, does it mean armv8a, armv8.1-a, etc? Hi Bradley, That's a good point. But also, what does "armv8a" mean?...

Hi everyone, I'm a member engineer of linaro's llvm team,coming from Spreadtrum.I am a new person on LLVM.Now I'm writing a Target Parser for AArch64,so options parsing of AArch64 about cpu & arch & fpu can be summary to one place. In the TargetParser,we assume "aarch64" and "arm64" are synonyms of armv8a(as they are only for armv8a,people usually do this). So after using AArch64TargetParser in options parsing in Cla...

I'm seeing a bunch of failures on AArch64 after updating this morning. These are NOT failing on x86-64. These all seem to be caused by segfaults (example backtrace below). Is anyone else seeing this? -David LLVM :: DebugInfo/symbolize-no-debug-str.test LLVM :: tools/gold/X86/comdat.ll LLVM :: tools/gold/X...

Hi folks, As Tim pointed out, we recently had the opportunity to collect 64-bit benchmark performance data for GCC 4.9, AArch64 and ARM64 compilers on a real hardware. It is a cortex-a53 device. Due to proprietary reasons we cannot share the full hardware configuration. The preliminary results were shared at the hackers lab at EuroLLVM yesterday. For those who could not make it, below is the summarized performance data....