search for: eabi_attribute

Hi, I do not get your result. Do I miss something? $COMP_ROOT/clang++ --target=arm-arm-eabihf -march=armv8.2a+fp16 arm.cpp -S -o - -O3 .text .syntax unified .eabi_attribute 67, "2.09" .eabi_attribute 6, 14 .eabi_attribute 7, 65 .eabi_attribute 8, 1 .eabi_attribute 9, 2 .fpu crypto-neon-fp-armv8 .eabi_attribute 12, 4 .eabi_attribute 36, 1 .eabi_attribute 42, 1 .eabi_attribute 34, 0 .eabi_at...

....2 can run on SimpleScalar. Now I want to use llvm/clang to generate ARM assembly code and arm-linux-gcc 2.95.2 to be assembler. Unfortunately, I got some error messages below : hello.s: Assembler messages: hello.s:1: Error: Unknown pseudo-op: `.syntax' hello.s:2: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:3: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:4: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:5: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:6: Error: Unknown pseudo-op: `.eabi_attribute' make: *** [all] Error 1 Then I try commends : $ clang...

On Feb 17, 2011, at 10:35 PM, Вадим Марковцев wrote: > Hello everyone, > > I've added the "S" suffixed versions of ARM and Thumb2 instructions to tablegen. Those are, for example, "movs" or "muls". > Of course, some instructions have already had their twins, such as add/adds, and I leaved them untouched. Adding separate "s" instructions is

...t; Now I want to use llvm/clang to generate ARM assembly code and arm-linux-gcc 2.95.2 to be assembler. > Unfortunately, I got some error messages below : > > hello.s: Assembler messages: > hello.s:1: Error: Unknown pseudo-op: `.syntax' > hello.s:2: Error: Unknown pseudo-op: `.eabi_attribute' > hello.s:3: Error: Unknown pseudo-op: `.eabi_attribute' > hello.s:4: Error: Unknown pseudo-op: `.eabi_attribute' > hello.s:5: Error: Unknown pseudo-op: `.eabi_attribute' > hello.s:6: Error: Unknown pseudo-op: `.eabi_attribute' > make: *** [all] Error 1 >...

Hi Jim, On Tue, Sep 25, 2012 at 10:52:58AM -0700, Jim Grosbach wrote: > These errors are from the assembler, not LLVM. Specifically, your binutils is > too old. Given that it doesn't even recognize the ".syntax" directive, they're > *very* much too old. You need to upgrade. > -Jim She said in her previous mail, P.S. Because I got error when I use

...ics-show-option > -fcolor-diagnostics -backend-option -vectorize-loops -o a.s -x c a.c > clang -cc1 version 3.3 based upon LLVM 3.3 default target armv7m-none-eabi > #include "..." search starts here: > End of search list. > > $ cat a.s > .syntax unified > .eabi_attribute 6, 10 > .eabi_attribute 9, 2 > .eabi_attribute 10, 5 > .fpu vfpv4 > .eabi_attribute 20, 1 > .eabi_attribute 21, 1 > .eabi_attribute 23, 3 > .eabi_attribute 24, 1 > .eabi_attribute 25, 1 > .eabi_attribute 44, 1 > .file "a....

Hello everyone, I've added the "S" suffixed versions of ARM and Thumb2 instructions to tablegen. Those are, for example, "movs" or "muls". Of course, some instructions have already had their twins, such as add/adds, and I leaved them untouched. Besides, I propose the codegen optimization based on them, which removes the redundant comparison in patterns like orr

...-math"="false" "use-soft-float"="false" } !llvm.ident = !{!0} !0 = metadata !{metadata !"Ubuntu clang version 3.4.0-2ubuntu1~trusty1 (tags/RELEASE_340/final) (based on LLVM 3.4.0)"} And here is what I see in MSP430 .text .syntax unified .cpu msp430 .eabi_attribute 6, 1 @ Tag_CPU_arch .eabi_attribute 8, 1 @ Tag_ARM_ISA_use .eabi_attribute 20, 1 @ Tag_ABI_FP_denormal .eabi_attribute 21, 1 @ Tag_ABI_FP_exceptions .eabi_attribute 23, 3 @ Tag_ABI_FP_number_model .eabi_attribute 24, 1 @ Tag_ABI_align_needed .eabi_attribute 25, 1 @ Tag_ABI_align_preserved .file &qu...

...-diagnostics -backend-option -vectorize-loops -o a.s -x c a.c >> clang -cc1 version 3.3 based upon LLVM 3.3 default target armv7m-none-eabi >> #include "..." search starts here: >> End of search list. >> >> $ cat a.s >> .syntax unified >> .eabi_attribute 6, 10 >> .eabi_attribute 9, 2 >> .eabi_attribute 10, 5 >> .fpu vfpv4 >> .eabi_attribute 20, 1 >> .eabi_attribute 21, 1 >> .eabi_attribute 23, 3 >> .eabi_attribute 24, 1 >> .eabi_attribute 25, 1 >> .eabi_attrib...

...-backend-option -vectorize-loops -o a.s -x c a.c > > clang -cc1 version 3.3 based upon LLVM 3.3 default target > armv7m-none-eabi > > #include "..." search starts here: > > End of search list. > > > > $ cat a.s > > .syntax unified > > .eabi_attribute 6, 10 > > .eabi_attribute 9, 2 > > .eabi_attribute 10, 5 > > .fpu vfpv4 > > .eabi_attribute 20, 1 > > .eabi_attribute 21, 1 > > .eabi_attribute 23, 3 > > .eabi_attribute 24, 1 > > .eabi_attribute 25, 1 > > .ea...

...foo(int* a){ bar(a); *a=42; } ### Generated assembly with target ARM $ clang --target=arm -S -O1 noreturn.c -o noreturn.s && cat noreturn.s clang: warning: unknown platform, assuming -mfloat-abi=soft clang: warning: unknown platform, assuming -mfloat-abi=soft .text .syntax unified .eabi_attribute 67, "2.09" @ Tag_conformance .cpu arm7tdmi .eabi_attribute 6, 2 @ Tag_CPU_arch .eabi_attribute 8, 1 @ Tag_ARM_ISA_use .eabi_attribute 17, 1 @ Tag_ABI_PCS_GOT_use .eabi_attribute 20, 1 @ Tag_ABI_FP_denormal .eabi_attribute 21, 1 @ Tag_ABI_FP_exceptions .eabi_attribute 23, 3 @ Tag_AB...

Dear list, git checkout llvmorg-8.0.0 -b llvm8.0 cmake -G "Unix Makefiles" ../llvm-project/llvm -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_PROJECTS="clang;lld" -DLLVM_TARGETS_TO_BUILD="X86;NVPTX;AMDGPU;ARM;AArch64" [arm.cpp] #define vst4_lane_f16(__p0, __p1, __p2) __extension__ ({ \ float16x4x4_t __s1 = __p1; \ __builtin_neon_vst4_lane_v(__p0, __s1.val[0],

Hi, I wanted to know if it was possible to force ARM backend to compile a function in ARM while the rest is in Thumb mode. I tried the attributes which is used in GCC but it doesn't work. Here is what I tried: https://pastebin.com/jCr5LPUY Thanks in advance, Uvekilledkenny -------------- next part -------------- An HTML attachment was scrubbed... URL:

...e arm-none-linux-gnueabi-gcc alias.c clang: warning: unknown platform, assuming -mfloat-abi=soft /tmp/cc-0BIpHn.s: Assembler messages: /tmp/cc-0BIpHn.s:1: Error: unknown pseudo-op: `.syntax' /tmp/cc-0BIpHn.s:2: Error: unknown pseudo-op: `.cpu' /tmp/cc-0BIpHn.s:3: Error: unknown pseudo-op: `.eabi_attribute' /tmp/cc-0BIpHn.s:4: Error: unknown pseudo-op: `.eabi_attribute' /tmp/cc-0BIpHn.s:5: Error: unknown pseudo-op: `.eabi_attribute' /tmp/cc-0BIpHn.s:6: Error: unknown pseudo-op: `.eabi_attribute' /tmp/cc-0BIpHn.s:7: Error: unknown pseudo-op: `.eabi_attribute' /tmp/cc-0BIpHn.s:8: Er...

...tdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /home/walsimou/embtoolkit.git/tools-armel-linux-arm920t/bin/../lib/gcc/armel-unknown-linux-gnueabi/4.7.3/crtend.o /home/walsimou/embtoolkit.git/sysroot-armel-linux-arm920t/usr/lib/crtn.o ----- CLANG/LLVM-3.2 assembly out-------- .syntax unified .eabi_attribute 6, 2 .eabi_attribute 20, 1 .eabi_attribute 21, 1 .eabi_attribute 23, 3 .eabi_attribute 24, 1 .eabi_attribute 25, 1 .file "test.ii" .text .globl main .align 2 .type main,%function main: push {r11, lr} mov r11, sp...

...-march=arm -mcpu=strongarm1100 hello.ll $ arm-linux-gcc -O3 -march=armv4 -mcpu=strongarm1100 -static -mfloat-abi=soft hello.s -o hello Unfortunately, I get some error messages: hello.s: Assembler messages: hello.s:1: Error: Unknown pseudo-op: `.syntax' hello.s:2: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:3: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:4: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:5: Error: Unknown pseudo-op: `.eabi_attribute' hello.s:6: Error: Unknown pseudo-op: `.eabi_attribute' make: *** [all] Error 1 I want to know my cross-compi...

...efault-synthesize-properties -fdiagnostics-show-option -fcolor-diagnostics -backend-option -vectorize-loops -o a.s -x c a.c clang -cc1 version 3.3 based upon LLVM 3.3 default target armv7m-none-eabi #include "..." search starts here: End of search list. $ cat a.s .syntax unified .eabi_attribute 6, 10 .eabi_attribute 9, 2 .eabi_attribute 10, 5 .fpu vfpv4 .eabi_attribute 20, 1 .eabi_attribute 21, 1 .eabi_attribute 23, 3 .eabi_attribute 24, 1 .eabi_attribute 25, 1 .eabi_attribute 44, 1 .file "a.c" .section .text.out_char,"ax&qu...

trying this: clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc a.c 2010/9/10 Emmanuel Blot <eblot.ml at gmail.com>: > Hello, > > Is there a quick tutorial to build the LLVM toolchain from a Linux or > Mac OS X x86 host for an ARM v4/v5/v6 ELF target? > It this configuration supported, and is it possible to build the

Hello, Is there a quick tutorial to build the LLVM toolchain from a Linux or Mac OS X x86 host for an ARM v4/v5/v6 ELF target? It this configuration supported, and is it possible to build the Clang compiler for this host/target combination? I know about the installation page, but I keep failing to build this toolchain with LLVM 2.7. Maybe it is not (yet) supported? Thanks, Manu

...ently. And I don't know how to write .s to test this without (PLT). NP. Can you just add that as a FIXME in elf-thumbfunc-reloc.ll? That way we know why it is there and can port it once more of the asm parser works. > Regarding elf-xscale-attribute.ll, those attributes are for > ".eabi_attribute" lines > in .s files and attributes in .aeabi section in .o files. Both .ll->.s > and .ll->.o > should be tested. Surely, not .s -> .o. I didn't write .ll -> .s because > ARMAsmParser ignore ".eabi_attribute" for now Since this is something that happen...