search for: doinitialplacement

...hich removed the entire ConstantIslands thing. It looks like the key points are creating a "CONSTPOOL_ENTRY" "instruction" which is emitted in the AsmPrinter. A relatively simple pass should be able to convert constpool entries as LLVM sees them into such instructions (see "doInitialPlacement"). Most of the complexity is in moving the constants around so that they're accessible from the instructions that use them, but for a first approximation that's not needed (beware, PlumHall's ch7_22 is a prime candidate for exercising this ability even with a 1MB range). Regards....

I am working towards a more complete solution for large constants in mips 16 (ala Arm constant islands and such). That is part of why I'm busy expanding all macros being emitted in the mips 16 compiler (almost done). I'm wondering if there is a poor mans approach for large constants that can be done very simply that I can add just for now. Gcc mips 16 places them after the function

Hi, I'd like to generate constants inside .text in order to use ip-relative loads, when the code model is "large". How can I do this? (I'm on X86_64 linux) Thank you. - Elena --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the

...switched to the x86 model back in February. Which means thar r175258 is a nice potted (but reversed) description of all the steps needed. Ignore the more baroque parts of AArch64ConstantIslandsPass.cpp, yours will probably only have to add a bunch of CONSTPOOL_ENTRYs at the end of the function (the doInitialPlacement method, though even that does more than you need). I'll watch with interest to see how you handle it, AArch64 will probably have the same issues in the large code model. Cheers. Tim.

...ire ConstantIslands thing. It looks like > the key points are creating a "CONSTPOOL_ENTRY" "instruction" which is > emitted in the AsmPrinter. A relatively simple pass should be able to > convert constpool entries as LLVM sees them into such instructions > (see "doInitialPlacement"). > > Most of the complexity is in moving the constants around so that > they're accessible from the instructions that use them, but for a > first approximation that's not needed (beware, PlumHall's ch7_22 is a > prime candidate for exercising this ability even with...