Displaying 5 results from an estimated 5 matches for "hwdiv".
Did you mean:
hwdev
2015 Jan 29
4
[LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing
Tim,
How about the below option ?
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. Specify the ".arch_extension idiv" which is available as an extension for my custom variant.
3. Teach LLVM & Clang about your CPU's features, either locally or upstream.
4. Pass "-mhwdiv=arm,thumb" to Clang (or less if yo...
2015 Jan 28
2
[LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing
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
2015 Jan 29
0
[LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing
...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. Specify the ".arch_extension idiv" which is available as an extension for my custom variant.
This looks like it'd be sufficient (and I didn't know about
.arch_extension at all, or I'd have mentioned it. Thanks!).
> 3. Teach...
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
Hi Daniel,
> (from the context, you might have meant 'tuple' where you've written
> 'triple'. I'm answering based on the assumption you meant 'triple')
>
>
I did mean what I wrote.
> The GNU triple is already used as a way of encoding a large amount of the
> target data in a string but unfortunately, while this data is passed
> throughout
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
Hi Eric,
Thanks for getting back to me on this.
> I'm not sure I agree with the basic idea of using the target triple as a way of
> encoding all of the pieces of target data as a string. I think in a number of
> cases what we need to do is either open up API to the back end to specify things,
> or encode the information into the IR when it's different from the generic triple.