search for: targetobjectfil

Hi, I would like to create an .init section in the LLVM backend. Can anyone shed me the light on how to do it? Do I have to create it in the clang? Thanks, Jin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161014/4f262397/attachment.html>

...into LLC, you can use the results of the MachineCodeEmitter and addPassesToEmitMachineCode. At this point, I'm not sure which way will work best for you. If possible, it would be nice if you could make your .o file writing code as target-independent as possible (potentially defining a new TargetObjectFile interface for any hooks you need). In particular, if MACH-SUIF is an ELF-based system, it would be nice to be able to use the ELF-specific routines to write X86-ELF or PPC-ELF files as well (assuming the hooks were implemented). Clearly you can choose to worry about this or not at your discr...

...mode. It accepts two arguments: source register and address (immediate). This instruction is not available in Mips, but it is in Hexagon, so I copied from Hexagon the following, adapting it to my registers: - In ISelLowering.h: CONST32 and CONST32_GP - In ISelLowering.cpp: LowerGlobalAddress - In TargetObjectFile.cpp: isGlobalInSmallSection - In InstrInfo.td: def SDTmyCONST32 : SDTypeProfile<1, 1, [ SDTCisVT<0, i32>, SDTCisVT<1, i32>, SDTCisPtrTy<0>]>;...

...lts > of the MachineCodeEmitter and addPassesToEmitMachineCode. At this point, > I'm not sure which way will work best for you. > > If possible, it would be nice if you could make your .o file writing code > as target-independent as possible (potentially defining a new > TargetObjectFile interface for any hooks you need). In particular, if > MACH-SUIF is an ELF-based system, it would be nice to be able to use the > ELF-specific routines to write X86-ELF or PPC-ELF files as well (assuming > the hooks were implemented). Clearly you can choose to worry about this >...

...a problem. We do not currently > support emitting .o files directly, but it has been planned for quite > some time. > > ... > > If possible, it would be nice if you could make your .o file writing > code as target-independent as possible (potentially defining a new > TargetObjectFile interface for any hooks you need). In particular, if > MACH-SUIF is an ELF-based system, it would be nice to be able to use the > ELF-specific routines to write X86-ELF or PPC-ELF files as well > (assuming the hooks were implemented). Clearly you can choose to worry > about this...