search for: emitstartofasmfil

Hi all, I'm trying to write a custom module-level pass that runs before AsmPrinter::EmitStartOfAsmFile(), since I'd like to have some processed information available once entering this function. Looking through "Writing an LLVM pass" documentation, it's not clear to me if this is possible. I've also tried putting the pass in different orders (addPreISel, addIRPasses, and etc....

...rMode4Operand (linked to ARMInstrInfo.td) that currently assume raw text support in the OutStreamer. Are these methods still supposed to be invoked in the MC'ized path for assembly output? Is JimG's new MC/.s ARMAsmPrinter::EmitInstruction() somehow bypassing these completely? and also on EmitStartOfAsmFile(), it emits a bunch of text assembly attributes - which is clearly wrong for MC (but is still being used in the asm emission). Can anyone suggest a better mechanism to switch on this than using OutStreamer.hasRawTextSupport()? Thanks, -Jason

...Instruction() somehow bypassing > these completely? > The ones in ARMAsmPrinter.cpp are now effectively unused, and I'll be removing them soon. I just need to do a bit of tablegen hacking first to be able to do so. The MC versions are in AsmPrinter/ARMInstPrinter.cpp. > and also on EmitStartOfAsmFile(), it emits a bunch of text assembly > attributes - which is clearly wrong for MC (but is still being used in > the asm emission). Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. > Can anyone suggest a...

...I would expect there to be an equivalent function to do what needs done for object files. Perhaps there isn't one (yet) and that's what's leading to the confusion? LOL :-) Yes, maybe that's it. Included is a patch w comments that explains better. Summation: 1. Should AsmPrinter::EmitStartOfAsmFile() be always called as is now? 2. If not, where should the arch-specific code go? 3. Where should the MCStreamer specific stuff for #2 go? Again, these are all high level design intent questions. Perhaps Mr Lattner can opine? Thanks! -jason > > -------------- next part -------------- A no...

Hi Jim, > Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. Attributes should be emitted into object file as well... -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Sep 29, 2010, at 3:58 PM, Anton Korobeynikov wrote: > Hi Jim, > >> Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. > Attributes should be emitted into object file as well... Yes, but surely not by a function explicitly indicated to be for assembly files. I would expect there to be an

...valent function to do what needs done for object files. Perhaps there isn't one (yet) and that's what's leading to the confusion? > > LOL :-) Yes, maybe that's it. Included is a patch w comments that > explains better. > > Summation: > > 1. Should AsmPrinter::EmitStartOfAsmFile() be always called as is now? Yes. > 2. If not, where should the arch-specific code go? N/A :-) > 3. Where should the MCStreamer specific stuff for #2 go? I'm not sure what you mean. The MCStreamer interface should have methods for all possible directives that can be sent to a .s f...

...hich registers (etc) it is using, in which >> class-method should I implement this ? >> > > These kinds of things should be emitted by the TGSI implementation of the > AsmPrinter class: http://llvm.org/docs/doxygen/html/classllvm_1_1AsmPrinter.html > You probably want to use EmitStartOfAsmFile() for the headers. Ok, is there an easy way to suppress the generation of: .text .file "/home/hans/foo.cl" .globl test_kern ? It seems I need to tackle all 3 of those separately ? >> 2) Immediates need to be declared with a specific >> value...

...a header > to declare which registers (etc) it is using, in which > class-method should I implement this ? > These kinds of things should be emitted by the TGSI implementation of the AsmPrinter class: http://llvm.org/docs/doxygen/html/classllvm_1_1AsmPrinter.html You probably want to use EmitStartOfAsmFile() for the headers. > 2) Immediates need to be declared with a specific > value and then addressed as IMM[x], how would I go about > this ? > I would recommend adding a pass that replaced immediates in the code with IMM file regitser accesses. > 3) The get_global_id call needs to...

Hi, After a few distractions I'm back to work on the llvm tgsi backend. I've added clang integration and I can now compile a simple opencl program to something which sort of looks like tgsi. You can find my latest work on this here: http://cgit.freedesktop.org/~jwrdegoede/llvm http://cgit.freedesktop.org/~jwrdegoede/clang (the latter may still need to sync) I've a little test

...not influence the target configuration. I didn't dig in those "Dwarf Version", "CodeView", "CodeViewGHash", "Debug Info Version" and others Objective-C related info in module level metadata. But I found several metadata info are handled at AsmPrinter::EmitStartOfAsmFile(Module &M), but there is no any similar interface in MC layer. ex. MCAsmBackend or MCStreamer. > I guess this starts to come from the other direction for me, then: what >>> purpose does the "target triple" in the module textual IR serve? I guess >>> it's n...

...gt; > I didn't dig in those "Dwarf Version", "CodeView", "CodeViewGHash", > "Debug Info Version" and others Objective-C related info in module level > metadata. > > > > But I found several metadata info are handled at > AsmPrinter::EmitStartOfAsmFile(Module &M), but there is no any similar > interface in MC layer. ex. MCAsmBackend or MCStreamer. > > > > > > I guess this starts to come from the other direction for me, then: what > purpose does the "target triple" in the module textual IR serve? I guess >...

...;Dwarf Version", "CodeView", "CodeViewGHash", >>> "Debug Info Version" and others Objective-C related info in module level >>> metadata. >>> > >>> > But I found several metadata info are handled at >>> AsmPrinter::EmitStartOfAsmFile(Module &M), but there is no any similar >>> interface in MC layer. ex. MCAsmBackend or MCStreamer. >>> > >>> > >>> > I guess this starts to come from the other direction for me, then: >>> what purpose does the "target triple" in t...

David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> 於 2020年1月11日 週六 上午2:03寫道： > Ah, OK - thanks for walking me through that. > > Fair enough, I think I understand the issue/tradeoff now - and that the > other module level metadata don't currently influence the target > configuration at this level? > > I'm not sure, I only know that the target-abi is decided