search for: arm1176

Hi, I have been reading about llvm and clang and vmkit, and must say: great work guys. So when i got my raspberry pi, and having read that llvm is better at arm than gcc, i compiled llvm on the pi. The pi has a soc with armv6 (i don't know what that means exactly though). The pi is not fast and llvm with clang compilation took 22 h, but worked. hurrah. Then i compiled llvm/clang with itself

> > $ qemu-arm -cpu ? > > Available CPUs: > > arm926 arm946 arm1026 arm1136 arm1136-r2 arm1176 arm11mpcore > > cortex-m3 > > cortex-a8 > > cortex-a8-r2 cortex-a9 cortex-a15 ti925t pxa250 sa1100 sa1110 > pxa255 pxa260 > > pxa261 pxa262 pxa270 pxa270-a0 pxa270-a1 pxa270-b0 pxa270-b1 xa270- > c0 > > pxa270-c5 any > > > > Still your proce...

On 12/16/14 3:53 AM, Kristof Beyls wrote: > I've been wondering too about how to get better ARM v6m compile-and-execute > testing going. > > As you say Jon, the non-execution-based regression tests are surprisingly > good at catching issues; but they're no full substitute for executing the > code produced by the backend for a reasonably-sized test suite. > > If

...s 43M 0 43M 0% /run/user/1000 $ lscpu: Architecture: armv6l Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 Vendor ID: ARM Model: 7 Model name: ARM1176 Stepping: r0p7 CPU max MHz: 700.0000 CPU min MHz: 700.0000 BogoMIPS: 697.95 Flags: half thumb fastmult vfp edsp java tls $ dovecot -n: # 2.3.7 (494d20bdc): /etc/dovecot/dovecot.conf # OS: Linux 4.14.50-2-ARCH armv6l # Hostname: alarmpi doveconf...

...o find library -lm > ld.lld: error: unable to find library -lclang_rt.builtins-armv6.a > clang-8: error: ld.lld command failed with exit code 1 (use -v to see > invocation) > Just to be sure; do you really mean --target=armv6-none-eabi ? That is targeting an old ArmV6 device such as an ARM1176 as used on the Raspberry Pi; this is very different from --target=armv6m-none-eabi , as used on the cortex-m0, despite there being only one letter difference in the target! Whichever you need you'll need to have the right compiler-rt. When you use a -none-eabi target clang will use the BareMe...

...brary -lm > ld.lld: error: unable to find library -lclang_rt.builtins-armv6.a > clang-8: error: ld.lld command failed with exit code 1 (use -v to see > invocation) > > Just to be sure; do you really mean --target=armv6-none-eabi ? That is > targeting an old ArmV6 device such as an ARM1176 as used on the > Raspberry Pi; this is very different from --target=armv6m-none-eabi , > as used on the cortex-m0, despite there being only one letter > difference in the target! Whichever you need you'll need to have the > right compiler-rt. > > When you use a -none-eabi tar...

...brary -lm > ld.lld: error: unable to find library -lclang_rt.builtins-armv6.a > clang-8: error: ld.lld command failed with exit code 1 (use -v to see > invocation) > > Just to be sure; do you really mean --target=armv6-none-eabi ? That is > targeting an old ArmV6 device such as an ARM1176 as used on the > Raspberry Pi; this is very different from --target=armv6m-none-eabi , > as used on the cortex-m0, despite there being only one letter > difference in the target! Whichever you need you'll need to have the > right compiler-rt. > > When you use a -none-eabi tar...

...8" -cc1 -triple armv6kz-unknown-linux-gnueabihf -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -discard-value-names -main-file-name hello.c -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu arm1176jzf-s -target-feature +strict-align -target-abi aapcs-linux -mfloat-abi hard -fallow-half-arguments-and-returns -dwarf-column-info -debugger-tuning=gdb -v -resource-dir /usr/local/myclang/lib/clang/8.0.0 -internal-isystem /usr/local/include -internal-isystem /usr/local/myclang/lib/clang/8.0.0/includ...