search for: aapcs_vfpcc

Forgot to reply all to include the list. deep ---------- Forwarded message ---------- From: Sandeep Patel <deeppatel1987 at gmail.com> Date: 2010/11/17 Subject: Re: [LLVMdev] Build Attributes Proposal To: Rafael Espíndola <rafael.espindola at gmail.com> 2010/11/17 Rafael Espíndola <rafael.espindola at gmail.com>: >> Another use for build attributes would be as a means

...l per-function as well. My favorite example is > __attribute__((pcs("aapcs-vfp"))) as a function attribute to select > the calling convention. > > Maybe these attributes could referenced like metadata so they can be > merged if identical? LLVM IR already represents that as aapcs_vfpcc function attribute. cheers, --renato

...vorite example is >> __attribute__((pcs("aapcs-vfp"))) as a function attribute to select >> the calling convention. >> >> Maybe these attributes could referenced like metadata so they can be >> merged if identical? > > LLVM IR already represents that as aapcs_vfpcc function attribute. Yes. The ARM attributes want to know what the CC is for the entire translation unit, which because of this very function attribute is not possible to accurately specify. If we treat them all as function attributes, then we have the same merge problem on the function level that...

> Hi Duncan, > > This could work, but it's very limited. Besides, there's already an MC > build attribute infrastructure, one would have to interpret those > strings in the back-end to an MC construct then back again to ASM and > ELF. > > I don't see why having a magic global would be worse than using module asm... So, you mentioned that there should be no