Displaying 3 results from an estimated 3 matches for "thumb16".
Did you mean:
thumb1
2010 Nov 16
1
[LLVMdev] Build Attributes Proposal
...tes
> that are specific to their own architecture, and as long as they don't
> collide with the public definitions, other manufacturers are free to
> ignore.
I think there are several common use cases for these attributes -
1. to mark what ISA a function is compiled for: (i.e. is it a
thumb16/thumb32/ARM?)
2. to constrain the generated code to use specific co-processors.
At least for case 2, the ARMTargetMachine/ARMSubtarget contains a
distinct set of flags which should be output in the file scope section
of the attributes
For case 1, I don't know how common it is for the same exec...
2010 Nov 13
0
[LLVMdev] Build Attributes Proposal
On 13 November 2010 21:15, Duncan Sands <baldrick at free.fr> wrote:
> Since I don't know anything about these attributes, talk of indexes and
> so forth goes straight over my head.
Hi Duncan,
I assumed you knew what build attributes were in the first place, my mistake.
For a full explanation of what they are, see ARM ABI Addenda, section
2.1 (PDF). (Google's first hit for
2010 Nov 13
2
[LLVMdev] Build Attributes Proposal
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