search for: namedmetadatastructure

Hi Chris, > From the design perspective, I think it would make sense to represent this in > LLVM IR with named metadata (http://llvm.org/docs/LangRef.html# > namedmetadatastructure) like "!llvm.fixedregs". This could then be picked up > by the code generator, installed as preallocated registers (Jakob would be the > one to ask how best to do this). -ffixed-<reg> and global register seems do the same thing, they both reserve register from being used b...

...w what I mean) compiler feature. This is one of the blocking issues preventing some portion of the Linux kernel from "just working" with LLVM. >From the design perspective, I think it would make sense to represent this in LLVM IR with named metadata (http://llvm.org/docs/LangRef.html#namedmetadatastructure) like "!llvm.fixedregs". This could then be picked up by the code generator, installed as preallocated registers (Jakob would be the one to ask how best to do this). If you're not in a huge hurry, an even better way to model this is with Bill Wendling's work on generalized funct...

On Oct 3, 2012, at 12:13 AM, 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote: > Hi Chris, > >> From the design perspective, I think it would make sense to represent this in >> LLVM IR with named metadata (http://llvm.org/docs/LangRef.html# >> namedmetadatastructure) like "!llvm.fixedregs". This could then be picked up >> by the code generator, installed as preallocated registers (Jakob would be the >> one to ask how best to do this). > > -ffixed-<reg> and global register seems do the same thing, they both > reserve regi...

I'm adding support for -ffixed-<reg> <http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Code-Gen-Options.html#index-ffixed-1435> for Hexagon and was wondering if I should do it in such a way that other targets get the support as well by default or if a given target back-end should have to explicitly opt-in for support. Any opinions? Matthew Curtis. -- Qualcomm Innovation Center,