search for: armed

Hi, Can someone who's familiar with lld take a look? [2980/3371] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/disassemble.c.o [2981/3371] Building CXX object tools/lld/COFF/CMakeFiles/lldCOFF.dir/Writer.cpp.o FAILED: tools/lld/COFF/CMakeFiles/lldCOFF.dir/Writer.cpp.o /opt/arm/arm-linux-compiler-20.0_Generic-AArch64_RHEL-7_aarch64-linux/bin/armclang++ -DGTEST_HAS_RTTI=0

The attached patches are against the v0.114 release and cover some of the tweaks I made while playing about testing ARM and Thumb support. Please review and consider applying. Even with the patches, ARM dynamic linking doesn't seem to work and the Thumb test applications seem to have shaken out a Thumb bug in the 2.4.21-rmk2 kernel which I'm still trying to track down. Still more fun to

Hi cschen, It seems that libunwind (the one included in libcxxabi) is mandatory at the moment. Use the second build command instead: $ CROSS_COMPILING=arm ENABLE_LIBUNWIND=1 ./scripts/compile-all.sh Logan On Tue, Oct 7, 2014 at 5:32 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > After do "sudo apt-get update", the following are pass. > > Install the

Hello, Thank you for your kind attention to my issue and your help. I changed the tool chain and tried again. And there is a little progress but still have some problem. Using --sysroot doesn't make clang use linker(ld) in the cross tool. Most important question is how I can make clang use cross tool linker. Let me show you my experiment and questions below. There are two questions. [Run]

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

On 10/3/14 10:16 AM, Dan Albert wrote: >> >> I try to build libc++ and libc++abi for host x86_64(linux) and target >> arm(linux) but fail. >> > > Failing in what way? If this isn't working out of the box, we've done > something wrong. Yeah, it would help to know more specifics about where you're getting stuck. > > jroelofs might know more... For

i try compile with options: binutils 2.20.1 ../configure --target=arm-unknown-linux-gnueabi --program-prefix=arm- --prefix=/home/kursh/arm --enable-gold --enable-plugins --with-sysroot=/home/kursh/arms/sys-root make && make install LLVM: CXXFLAGS="-fPIC" ../configure \ --enable-jit \ --enable-optimized \ --enable-shared\ --enable-pic\ --with-pic\

Not just dom0. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- xen/arch/arm/domain.c | 3 +++ xen/arch/arm/domain_build.c | 3 --- xen/arch/arm/p2m.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xen/arch/arm/domain.c b/xen/arch/arm/domain.c index 5702399..4b38790 100644 --- a/xen/arch/arm/domain.c +++ b/xen/arch/arm/domain.c @@

2015-03-11 16:22 GMT-05:00 Richard Gorton < rcgorton at cognitive-electronics.com>: > I can confirm that musl builds and works correctly with clang/llvm. We > are using musl as a libc for our architecture. > It has a much smaller code footprint than newlib or glibc. > I successfully cross-compile the must-libc using clang, with the configuration: C=clang

Hello > ./clang -v -emit-llvm -ccc-host-triple arm-none-linux-gnueabi > -I/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/include > -L/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin hello.c You forgot about sysroot here. > /home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin/ld: > unrecognised emulation mode: armelf_linux_eabi >

Hello everyone, The review http://reviews.llvm.org/D20951 implements initial support for the ARM architecture in LLD. To keep the patch size down, and to avoid the complexities of interworking between ARM and Thumb, there is just enough support for an ARM only Hello World to link and run on ARM Linux [*]. My main aim is to get this functionality committed as the basis of an ARM port and would

The parts of klibc specific to the arm architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 1eff7c685b36cd0120694fd4150b32a26168d926 tree 953dd1dbd2e994fc27c6cf5708fcbe06fe000d58 parent 5e5ce29210ac33a0b3704eb9ab5e5d5b55375575 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:16 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Dear all, I have a problem while compiling the ARM assembly file produced by LLVM arm backend (llc)。 The commands I did are .. llc -march=arm printf.bc -o printf.arm.s arm-softfloat-linux-gnu-as printf.arm.s -o printf.arm.o arm-softfloat-linux-gnu-ld --dynamic-linker /home/toolchain/arm-softfloat-linux-gnu/distributed/arm-softfloat-linux-gnu/lib/ld-2.3.5.so

Hello, on the problems cross-building compiler-rt: Tried to follow https://llvm.org/docs/HowToCrossCompileBuiltinsOnArm.html which lead to this cmake: cmake -G "Ninja" ../llvm/projects/compiler-rt/ -DCOMPILER_RT_BUILD_BUILTINS=ON -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF -DCOMPILER_RT_BUILD_LIBFUZZER=OFF -DCOMPILER_RT_BUILD_PROFILE=OFF

Hello, I am trying to cross compile LLVM. Build and compile on Mac OS X 10.5.7 Target is an Angstrom Linux Cortex-A8 Beagle board. I would like to avoid GPLv3. I can compile. But when I run my executable on Beagle crt0.S is calling an AngelSWI to setup the heap and stack. But the AngelSWI seems to just be a stub because it returns zeros for the pointers. That leads to a segfault. If I hack in

Hello Christian, I'd expect that adding the library paths (-L) from gcc -v should fix the unable to find -lc, -lm but it won't fix the -lclang_rt.builtins-armv6m.a . To get clang_rt.builtins-armv6m.a you will need to cross compile compiler-rt for v6m and copy it to /usr/local/myclang/lib/clang/8.0.0/lib/baremetal . Beware that building compiler-rt for v6m does need quite a bit of fighting

Hello Christian, I've put some comments inline, On Sun, 3 Feb 2019 at 13:11, Christian Richter <christian.richter at hsu-hh.de> wrote: > > Hello again, > > so after I successfully build the compiler-rt for armv6 I tried to > actually use it in compiling a small helloworld for a baremetal arm > (consisting of barehelloCLANG.c and a small io.h + io.c) , but the >

Hello, With your kind concern and help, I now can make a binary for ARM target. ./clang -v --save-temps -ccc-host-triple arm-none-linux-gnueabi --sysroot=/home/hum/Documents/Projects/arm_toolchain/arm-2010.09/arm-none-linux-gnueabi/libc -gcc-toolchain /home/hum/Documents/Projects/arm_toolchain/arm-2010.09 hello.c -o hello The build command is shown above. After that, I prepared an ARM laptop,

Hi, I try to build llvm-trunk with Cmake (gcc-5.3.0 is necessary for CUDA) on my "SUSE Linux Enterprise Server 12.2 (x86_64)". svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm cd llvm/tools svn co http://llvm.org/svn/llvm-project/cfe/trunk clang svn co http://llvm.org/svn/llvm-project/polly/trunk polly cd clang/tools svn co

Hello, I am building llvm-gcc4.2-2.6 for ARM target.I used the next command line option: >> .../configure --enable-languages=c,c++ --enable-checking --target=arm-eabi >> and then >> make target_alias=arm-eabi >> And then I obtain the following error: In file included from ../../gcc/config/arm/arm.c:59: ../../../libcpp/internal.h: In function ‘ufputs’: