search for: cpustringisvalid

...; to Clang (or less if you only have hwdiv in one mode). --Sumanth G -----Original Message----- From: Tim Northover [mailto:t.p.northover at gmail.com] Sent: Tuesday, January 27, 2015 6:44 PM To: Sumanth Gundapaneni Cc: LLVM Developers Mailing List; Roman Divacky; Ana Pazos Subject: Re: [LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing Hi Sumanth, > Shouldn’t the eabi attributes be honored ? EABI attributes are instructions for the linker on which object files are compatible with each other, not instructions for the assembler (and trying to make them so sounds like a re...

On 29 January 2015 at 03:36, Tim Northover <t.p.northover at gmail.com> wrote: > These ought to be unneeded if you do 1+2 above. As far as I remember, .arch_extension does change the assembler flags to support whatever you set. Have you tried that? cheers, --renato

...your guidance guys. > --Sumanth G > -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: Thursday, January 29, 2015 9:03 AM > To: Tim Northover > Cc: Sumanth Gundapaneni; Roman Divacky; LLVM Developers Mailing List > Subject: Re: [LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it > for ARM .cpu parsing > > On 29 January 2015 at 03:36, Tim Northover <t.p.northover at gmail.com> > wrote: >> These ought to be unneeded if you do 1+2 above. > > As far as I remember, .arch_extension does change the assembler flags to...

Hi Divacky, I have an armv7 variant that supports hardware division (extension). For my variant, I use ".cpu cortex-a9" and division attribute(.eabi_attribute 44, 2 @ Tag_DIV_use) to let the assembler do the right thing if it encounters a division instruction. With your path, the .cpu directive is used to fetch the available features of a CPU and ignores the eabi attributes. What

> How about the below option ? My options were mutually exclusive, or at least any one of them would allow you to assemble code using sdiv/udiv. You probably don't need to combine them. > 1. Specify an existing generic armv7 CPU or the CPU which is close my custom variant. My custom variant can be treated as "cortex-a9" + hwdiv. So my CPU here is "cortex-a9" > 2.