search for: armeb

...). Default target: x86_64-unknown-linux-gnu Host CPU: ivybridge Registered Targets: aarch64 - AArch64 (little endian) aarch64_be - AArch64 (big endian) amdgcn - AMD GCN GPUs arm - ARM arm64 - ARM64 (little endian) armeb - ARM (big endian) bpf - BPF (host endian) bpfeb - BPF (big endian) bpfel - BPF (little endian) cpp - C++ backend hexagon - Hexagon mips - Mips mips64 - Mips64 [experimental] mips64el - Mips6...

Hi Guys , We are trying to enable LTO on our code base for clang(3.8) using gold linker , and we are stuck with below error bash-4.1$ /arm-install/bin/armeb-linux-gnueabi-ld.gold --be8 /arm-install/bin/armeb-linux-gnueabi-ld.gold: --be8: unknown option And found that ,Be8 (byte invariant addressing) is not supported in the gold linker, Questions is ,how do we go from here ? Do be8 format is very mandatory for armv7(big endian) ? Or we can proc...

...ions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64 (little endian) aarch64_be - AArch64 (big endian) amdgcn - AMD GCN GPUs arm - ARM arm64 - ARM64 (little endian) armeb - ARM (big endian) cpp - C++ backend hexagon - Hexagon mips - Mips mips64 - Mips64 [experimental] mips64el - Mips64el [experimental] mipsel - Mipsel msp430 - MSP430 [experimental] nvptx - NVIDIA PTX 32-bit nvptx64 - NVID...

Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once

...r messages: Error: unknown architecture `armv6l' Error: unrecognized option -march=armv6l make[2]: *** [src/k6opt.o] Error 1 ? Here are the lines in the Makefile - ifeq (, $(findstring $(OSARCH) , Darwin SunOS )) ifeq (, $(findstring $(PROC) , x86_64 amd64 ultrasparc sparc64 arm armv5b arm5b armeb hppa2.0 ppc powerpc ppc64 ia64 s390 bfin mipsel mips)) ifeq (, $(findstring $(shell uname -m) , ppc ppc64 alpha armv4l arm5b armv5b armv61 armv7l s390 )) OPTIMIZE+=-march=$(PROC) endif endif endif gcc is - Thread model: posix gcc version 4.6.3 (Debian 4.6.3-14+rpi1) # uname -m armv6l Doug ---...

...idge >> >> Registered Targets: >> aarch64 - AArch64 (little endian) >> aarch64_be - AArch64 (big endian) >> amdgcn - AMD GCN GPUs >> arm - ARM >> arm64 - ARM64 (little endian) >> armeb - ARM (big endian) >> bpf - BPF (host endian) >> bpfeb - BPF (big endian) >> bpfel - BPF (little endian) >> cpp - C++ backend >> hexagon - Hexagon >> mips - Mips >>...

...Registered Targets: > aarch64 - AArch64 (little endian) > aarch64_be - AArch64 (big endian) > amdgcn - AMD GCN GPUs > arm - ARM > arm64 - ARM64 (little endian) > armeb - ARM (big endian) > bpf - BPF (host endian) > bpfeb - BPF (big endian) > bpfel - BPF (little endian) > cpp - C++ backend > hexagon - Hexagon > mips...

...ols to do cross compilation using my clang/LLVM based compiler and associated support programs and libraries. I have one set of download binaries available, for Fedora 16 x86_64 systems. The download includes the compiler, binutils, gdb, precompiled standard libraries and qemu support for arm, armeb, i386, microblaze, mips, mipsel, ppc, ppc64, and x86_64. The library source is also included. C has been most extensively tested, but limited C++ functionality is available. The major thing missing from C++ is libunwind. The download is available at http://ellcc.org/download.html I'm still...

...job. The new release looks great! http://ellcc.org I've also started to port libunwind into ELLCC. That's the last step for a fully non-gnu run-time environment: libcxx/libcxxabi/libunwind/musl/compiler-rt for C and C++ under Linux. Support for creating Linux executables in C for arm, armeb, mips, mipsel, ppc, microblaze, i386, and x86_64 looks good, ppc64 is coming along. -Rich

...ian no target list i386-softmmu x86_64-softmmu arm-softmmu cris-softmmu m68k-softmmu mips-softmmu mipsel-softmmu mips64-softmmu mips64el-softmmu ppc-softmmu ppcemb-softmmu ppc64-softmmu sh4-softmmu sh4eb-softmmu sparc-softmmu i386-linux-user x86_64-linux-user alpha-linux-user arm-linux-user armeb-linux-user cris-linux-user m68k-linux-user mips-linux-user mipsel-linux-user ppc-linux-user ppc64-linux-user ppc64abi32-linux-user sh4-linux-user sh4eb-linux-user sparc-linux-user sparc64-linux-user sparc32plus-linux-user gprof enabled no sparse enabled no profiler no static build...

As part of my ELLCC project (http://ellcc.org), I build clang/LLVM on my native x86_64 Linux box and then use it to compile itself. For further sanity checking, I then use that copy to cross compile for other targets (arm, armeb, i386, microblaze, mips, mipsel, ppc, and x86_64). After updating to a recent TOT revision, r195452, I get a strange error when cross compiling for the i386: llvm[2]: Compiling MCObjectSymbolizer.cpp for Release+Asserts build PHI node has multiple entries for the same basic block with different...

...Registered Targets: >>> aarch64 - AArch64 (little endian) >>> aarch64_be - AArch64 (big endian) >>> amdgcn - AMD GCN GPUs >>> arm - ARM >>> arm64 - ARM64 (little endian) >>> armeb - ARM (big endian) >>> bpf - BPF (host endian) >>> bpfeb - BPF (big endian) >>> bpfel - BPF (little endian) >>> cpp - C++ backend >>> hexagon - Hexagon >>> mips...

Hi all, Actually,I found there is a same problem for arm.For this case,I think > maybe we can play a trick in the clang. > 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

> > The Triple object will remain unchanged. > > The Tuple will be the API to handle getting/setting parameters > depending on the Triple, compiler flags, attributes, etc. > > This part doesn't seem obvious from the direction the patches are going. > There will be no string representation of all options, as that would > be impossible, or at least, highly

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

...no > target list i386-softmmu x86_64-softmmu arm-softmmu cris-softmmu m68k-softmmu mips-softmmu mipsel-softmmu mips64-softmmu mips64el-softmmu ppc-softmmu ppcemb-softmmu ppc64-softmmu sh4-softmmu sh4eb-softmmu sparc-softmmu i386-linux-user x86_64-linux-user alpha-linux-user arm-linux-user armeb-linux-user cris-linux-user m68k-linux-user mips-linux-user mipsel-linux-user ppc-linux-user ppc64-linux-user ppc64abi32-linux-user sh4-linux-user sh4eb-linux-user sparc-linux-user sparc64-linux-user sparc32plus-linux-user > gprof enabled no > sparse enabled no > profiler n...

...ian no target list i386-softmmu x86_64-softmmu arm-softmmu cris-softmmu m68k-softmmu mips-softmmu mipsel-softmmu mips64-softmmu mips64el-softmmu ppc-softmmu ppcemb-softmmu ppc64-softmmu sh4-softmmu sh4eb-softmmu sparc-softmmu i386-linux-user x86_64-linux-user alpha-linux-user arm-linux-user armeb-linux-user cris-linux-user m68k-linux-user mips-linux-user mipsel-linux-user ppc-linux-user ppc64-linux-user ppc64abi32-linux-user sh4-linux-user sh4eb-linux-user sparc-linux-user sparc64-linux-user sparc32plus-linux-user gprof enabled no sparse enabled no profiler no static build...