search for: tag_cpu_arch

...GNU_Linux/arm-none-linux-gnueabi/libc/thumb2/usr/lib/libc.a | grep dso_handle.o -A 10 File: /home/emitrax/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/arm-none-linux-gnueabi/libc/thumb2/usr/lib/libc.a(dso_handle.o) Attribute Section: aeabi File Attributes Tag_CPU_name: "7-A" Tag_CPU_arch: v7 Tag_CPU_arch_profile: Application Tag_ARM_ISA_use: Yes Tag_THUMB_ISA_use: Thumb-2 Tag_ABI_PCS_wchar_t: 4 Tag_ABI_FP_denormal: Needed Tag_ABI_FP_exceptions: Needed while $ arm-none-linux-gnueabi-readelf -A system.cpp.o Attribute Section: aeabi File Attributes Tag_CPU_name: "...

On 22 July 2012 22:03, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > While we are at it, if a new comer would like to understand where everything > takes place, where should he look? > > I did a grep in the source and eventually ended up in clang/something/driver. That's pretty much it: clang/lib/Driver

...e" "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 "simple-fadd.ll&qu...

...cribe this in the BuildAttributes we would need to use per Section or per Function attributes though. My suggestion to move forward here is: - Recreate the SubtargetInfo based on the merge of all the Targets and CPU information that we have seen, or warn/error if they are incompatible. - Ouput the Tag_CPU_arch BuildAttributes based on the merge of all the Targets and CPU information that we have seen. It is probably worth moving any discussion of this particular part to PR36542 since it is somewhat Arm specific. I'll add this comment to there. >> >> My personal preference is that we sho...

...we > would need to use per Section or per Function attributes though. > > My suggestion to move forward here is: > - Recreate the SubtargetInfo based on the merge of all the Targets and > CPU information that we have seen, or warn/error if they are > incompatible. > - Ouput the Tag_CPU_arch BuildAttributes based on the merge of all the > Targets and CPU information that we have seen. > > It is probably worth moving any discussion of this particular part to > PR36542 since it is somewhat Arm specific. I'll add this comment to > there. I'm not so sure this is ARM...

On Sun, Jul 22, 2012 at 9:42 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Any suggestions? > Try to specify CPU explicitly. Already did. clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3 fatal error: error in backend: CPU: 'cortex-m3' does not support ARM mode execution! S.

> clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple > thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3 > fatal error: error in backend: CPU: 'cortex-m3' does not support ARM > mode execution! Ok, and what's about -mthumb then? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi Logan, There are some tests in the MC/ARM directory that seem suspicious: directive-arch-armv{2,3}.s They expect "armv2" and "armv3" to have an "ARM v4" tag, which is wrong. I know GCC does that, but I don't think we should. Given that this will probably never happen in LLVM, I think we can safely take the correct approach and ignore GCC. Any other reason

Hi Logan, FYI, I spoke with Saleem on IRC, and we agree that this should be pre-v4. We don't expect any issues to come, so we should worry about them if there are any. cheers, --renato On 27 May 2015 at 17:26, Renato Golin <renato.golin at linaro.org> wrote: > Hi Logan, > > There are some tests in the MC/ARM directory that seem suspicious: > directive-arch-armv{2,3}.s >

...#39;t understand why, but it uses armv5te instead of thumb2. $ clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-gnueabi testReference.cpp -c $ arm-none-linux-gnueabi-readelf -A testReference.o Attribute Section: aeabi File Attributes Tag_CPU_name: "5TE" Tag_CPU_arch: v5TE Tag_ARM_ISA_use: Yes Tag_THUMB_ISA_use: Thumb-1 Tag_ABI_FP_denormal: Needed Tag_ABI_FP_exceptions: Needed Tag_ABI_FP_number_model: IEEE 754 Tag_ABI_align_needed: 8-byte Tag_ABI_align_preserved: 8-byte, except leaf SP Tag_DIV_use: Not allowed I realized this only when I moved...

On Wed, Jul 18, 2012 at 5:45 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 15:46, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> $ clang++ -ccc-host-triple thumbv7m-none-gnueabi noInclude.cpp -c >> --sysroot=/home/emitrax/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi/libc/ > > Try -ccc-gcc-name

On 18 July 2012 15:46, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > $ clang++ -ccc-host-triple thumbv7m-none-gnueabi noInclude.cpp -c > --sysroot=/home/emitrax/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi/libc/ Try -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-linux-gnueabi Sometimes it's better than sysroot, as it finds it

...m -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_ABI_FP_number_model .eabi_attribute 34, 0 @ Tag_CPU_unaligned_access .eabi_attribute 24, 1...

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:

On 3/15/2018 9:43 AM, Peter Smith via llvm-dev wrote: > Hello everyone, this is most likely Arm specific, but could affect > other targets where there is a somewhat complex relationship between > the triple and mcpu option. > > At present when clang is used as a linker driver for the gold-plugin > and when using and an explicit -mcpu is not given to clang, then clang > will

Hello everyone, this is most likely Arm specific, but could affect other targets where there is a somewhat complex relationship between the triple and mcpu option. At present when clang is used as a linker driver for the gold-plugin and when using and an explicit -mcpu is not given to clang, then clang will always generate a -Wl,-plugin-opt=mcpu=<default CPU> where the default CPU is based