search for: tag_advanced_simd_arch

...8 has NEON, while the ARM tool chain does not. So, if you compile a file with Clang for Cortex-A8 and link with LLVM linker (or LD), everything works fine, because that assumption is in every step of the tool chain. However, if you try to link with armlink, it won't work, as the NEON attribute (Tag_Advanced_SIMD_arch) will not be there, and when it finds vector instructions, it'll bail out. Another example I quote from the ABI: "The compiler might choose to use only the Thumb ISA in a specific build of a source file. Nonetheless, the relocatable file should be tagged as having been permitted to use t...

Hi Renato, > On 13 November 2010 15:12, Duncan Sands<baldrick at free.fr> wrote: >> I agree that it's limited. As for MC, it will need to handle these strings >> anyway since this is an existing LLVM feature (coming from gcc originally) >> that needs to be supported. > > Do you mean that LLVM-GCC generates build attributes as asm strings in IR? no, I mean

...e ARM tool chain does not. So, if you compile a file > with Clang for Cortex-A8 and link with LLVM linker (or LD), everything > works fine, because that assumption is in every step of the tool > chain. However, if you try to link with armlink, it won't work, as the > NEON attribute (Tag_Advanced_SIMD_arch) will not be there, and when it > finds vector instructions, it'll bail out. > > Another example I quote from the ABI: > > "The compiler might choose to use only the Thumb ISA in a specific > build of a source file. > Nonetheless, the relocatable file should be tagged...