[llvm-commits] Obtaining CPU information in RuntimeDyld

[Eric Christopher]

(That poor other guy at my misspelled email address)

Anyhow, I think the best way is just to get it via the object file.

-eric

On Mon, Oct 29, 2012 at 10:11 AM, Amara Emerson <amara.emerson at arm.com> wrote:
> Hi,
>
> I'm trying to improve the stub/call veneer generation, however for the older
> ARMv4t cores, BLX isn't a supported instruction. This means that without
> more architecture info, either we don't optimize it at all and stick with
> the current generic solution or we optimize for ARMv5 and above and break
> any ARM-Thumb interworking on the JIT for v4t and older targets.
>
> Thanks,
> Amara
>
> -----Original Message-----
> From: Jim Grosbach [mailto:grosbach at apple.com]
> Sent: 29 October 2012 17:05
> To: Amara Emerson
> Cc: llvm-commits at cs.uiuc.edu; ecristo at gmail.com
> Subject: Re: Obtaining CPU information in RuntimeDyld
>
> Hi Amara,
>
> What are you trying to do?
>
> -Jim
>
> On Oct 29, 2012, at 10:02 AM, Amara Emerson <amara.emerson at arm.com> wrote:
>
>> Hi,
>>
>> I'm unsure about the best way to obtain the specific CPU core that is
> being
>> targeted in the ExecutionEngine/RuntimeDyld component. It seems currently
>> the only way to find information like this is via the object file itself.
>> E.g. RuntimeDyld.cpp:65 where the Arch is retrieved via libObject.
>>
>> What would be the best way to get more information about the CPU type?
> _If_
>> passing more information to RuntimeDyld from the client isn't an option
> for
>> design reasons, then the only other choice I can see is to implement build
>> attribute reading in libObject/ELF.
>>
>> Thoughts?
>>
>> Amara
>>
>>
>>
>
>
>
>
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits