search for: armv

...e > > As you can see, I'm using CMake. Works pretty well so far. Hopefully > something like this will work for you as well? > I tried "cmake ../compiler-rt -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DLLVM_NATIVE_ARCH=ARM -DLLVM_TARGETS_TO_BUILD=ARM -DTARGET_TRIPLE=armv-none-linux-gnueabi -DCMAKE_CROSSCOMPILING=True". It will still build X86_64 version. I also tried "cmake ../compiler-rt -DCMAKE_C_COMPILER=/usr/local/arm-2009q3/bin/arm-none-linux-gnueabi-gcc -DCMAKE_CXX_COMPILER=/usr/local/arm-2009q3/bin/arm-none-linux-gnueabi-g++ -DLLVM_NATIVE_ARCH=A...

...ang. > Checking whether the given arch valid or not,before we throw it to the > parser,which can be used for both arm > and aarch64. For the actions I mentioned above,I wrote a check function as below, basing on the naming rules of the arm architecture. +//Only if -march startwith "armv" or "v" or "iwmmxt" or "xscale",it can be seen valid and sended to TargetParser +//for further parsing +static bool checkArchValid(StringRef Arch) +{ + if ((Arch.startswith("armv")) || Arch[0] == 'v' || + (Arch.startswith("iwmmxt&qu...

Hi Logan, There are some tests in the MC/ARM directory that seem suspicious: directive-arch-armv{2,3}.s They expect "armv2" and "armv3" to have an "ARM v4" tag, which is wrong. I know GCC does that, but I don't think we should. Given that this will probably never happen in LLVM, I think we can safely take the correct approach and ignore GCC. Any other reaso...

Notice!! sorry for that, the patch is incorrect, i attached the new one. -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- A non-text attachment was scrubbed... Name: triple.patch Type: application/octet-stream Size: 3745 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090815/9429c396/attachment.obj>

...We don't expect any issues to come, so we should worry about them if there are any. cheers, --renato On 27 May 2015 at 17:26, Renato Golin <renato.golin at linaro.org> wrote: > Hi Logan, > > There are some tests in the MC/ARM directory that seem suspicious: > directive-arch-armv{2,3}.s > > They expect "armv2" and "armv3" to have an "ARM v4" tag, which is wrong. > > I know GCC does that, but I don't think we should. Given that this > will probably never happen in LLVM, I think we can safely take the > correct approach and...

Hi, I've cross-compiled musl-libc to arm binaries with clang. It needs functions from static runtime library "libcompiler_rt.a". I tried to build compile_rt outside the llvm source tree. Using command like "make clang_linux", I can easily build "libcompiler_rt.a" for my host machine, which is X86_64. But how can I *cross-compile* the compiler_rt runtime

...rks pretty well so far. Hopefully >>> something like this will work for you as well? >>> >> >> I tried "cmake ../compiler-rt -DCMAKE_C_COMPILER=clang >> -DCMAKE_CXX_COMPILER=clang++ -DLLVM_NATIVE_ARCH=ARM >> -DLLVM_TARGETS_TO_BUILD=ARM -DTARGET_TRIPLE=armv-none-linux-gnueabi >> -DCMAKE_CROSSCOMPILING=True". It will still build X86_64 version. >> >> I also tried "cmake ../compiler-rt >> -DCMAKE_C_COMPILER=/usr/local/arm-2009q3/bin/arm-none-linux-gnueabi-gcc >> -DCMAKE_CXX_COMPILER=/usr/local/arm-2009q3/bin/arm-...

Hello, would it be possible to update config.sub and config.guess to the latest versions (or at least version from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU? Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284 Thanks, Petr

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? AArch64? AArch32? I guess we could use the triple (which has aarch64 or arm in it), but then it will need the triple or else we'll have a problem, since the current interpretation of "ar...

...m home page. Resulting bitcode runs great in interpreter, but it doesn't use JIT. From what I understand from LLVM that it is because of target triple or datalayout. On PC in my case target triple is "i386-mingw32", but LLVM JIT for ARM expects something that starts with "armv" or "thumb". Also datalayout differs a lot. If I understand correctly that is because bitcode actually contains some of platform specific optimizations (like integer endianness), so I can't simply change target triple string and everything will run. What I am now doing, is...

...ng bitcode runs great in interpreter, but > it doesn't use JIT. From what I understand from LLVM that it is > because of target triple or datalayout. On PC in my case target > triple is "i386-mingw32", but LLVM JIT for ARM expects something > that starts with "armv" or "thumb". Also datalayout differs a lot. > If I understand correctly that is because bitcode actually contains > some of platform specific optimizations (like integer endianness), > so I can't simply change target triple string and everything will run. > >...

...nst. I belive ARM Darwin might have a similar issue but i dont know how to fix it on that platform. ARM Darwin gurus please enlighten me how memory barriers are performed for ARM on Darwin. The kernel helper are implemented in http://kernel.ubuntu.com/git-repos/rtg/linux-2.6/arch/arm/kernel/entry-armv.S of the Linux sourcetree. /* * Reference prototype: * * void __kernel_memory_barrier(void) * * Input: * * lr = return address * * Output: * * none * * Clobbered: * * none * * Definition and user space usage example: * * typedef void (__kernel_dmb_t)(void); * #define __kernel_d...

Hi Tim, thanks for the swift response! @debug is defined in the same module, which makes this all the more confusing. The target information from the working example are: target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64" target triple = "armv6kz--linux-gnueabihf" from the ghc produced module: target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64" target triple = "arm-unknown-linux-gnueabihf" However there ones more thing, I could think of, arm does allow mixed mode I believe. And as such as the...

...Resulting bitcode runs great in interpreter, but it > doesn't use JIT. From what I understand from LLVM that it is because > of target triple or datalayout. On PC in my case target triple is > "i386-mingw32", but LLVM JIT for ARM expects something that starts > with "armv" or "thumb". Also datalayout differs a lot. If I understand > correctly that is because bitcode actually contains some of platform > specific optimizations (like integer endianness), so I can't simply > change target triple string and everything will run. > > What...

Dear testers, Release Candidate 2 has just been tagged [1]. Please build, test, and upload to the sftp. I know there are still outstanding issues from RC1, but there have been a lot of merges going into the branch and I think it's time for another round of RC testing. This RC comes a little behind schedule, sorry about that, but I'm still optimistic about hitting the target of releasing

...2): d3dx9: Add D3DXConvertMeshSubsetToSingleStrip stub. d3dx9/tests: Add D3DXSaveSurfaceToFileInMemory DDS header tests. Andrew Eikum (1): oleaut32: Don't clear BSTR size. Andrey Gusev (1): wine.inf: Fix LanguagePack entry. Andr? Hentschel (4): winebuild: Detect armv* toolchains. winegcc: Sync toolchain detection with winebuild. configure: Get rid of the prog parameter in WINE_CHECK_MINGW_PROG. configure: Detect MinGW-w64 Clang cross toolchain. Austin English (5): pdh: Add PdhBindInputDataSourceA/W stubs. ndis.sys: Add NdisAllocat...

...+++ b/dib/utils.ml @@ -33,7 +33,7 @@ let current_arch () = match Config.host_cpu with | "amd64" | "x86_64" -> "amd64" | "i386" | "i486" | "i586" | "i686" -> "i386" - | arch when string_prefix arch "armv" -> "armhf" + | arch when String.is_prefix arch "armv" -> "armhf" | arch -> arch let output_filename image_name = function @@ -47,12 +47,12 @@ let log_filename () = let var_from_lines var lines = let var_with_equal = var ^ "=" in -...

Just refactoring. Rich.

Hide/prevent the use of bad string functions like String.lowercase. These are replaced by safe functions that won't break UTF-8 strings. Other miscellaneous refactoring. Rich.

...= + (* Turn a CPU into the dpkg architecture naming. *) + let normalize_arch = function + | "amd64" | "x86_64" -> "amd64" + | "i386"| "i486" | "i586" | "i686" -> "i386" + | arch when string_prefix arch "armv" -> "armhf" + | arch -> arch in + normalize_arch Config.host_cpu + +let output_filename image_name = function + | fmt -> image_name ^ "." ^ fmt + +let log_filename () = + let tm = Unix.gmtime (Unix.time ()) in + sprintf "%s-%d%02d%02d-%02d%02d%02d.log&quo...