search for: powerpcasmprinter

...PIC16 -> Support PIC16 -> Target PIC16AsmPrinter -> AsmPrinter PIC16AsmPrinter -> CodeGen PIC16AsmPrinter -> Core PIC16AsmPrinter -> MC PIC16AsmPrinter -> PIC16 PIC16AsmPrinter -> PIC16Info PIC16AsmPrinter -> Support PIC16AsmPrinter -> Target PowerPCInfo -> Support PowerPCAsmPrinter -> AsmPrinter PowerPCAsmPrinter -> CodeGen PowerPCAsmPrinter -> Core PowerPCAsmPrinter -> MC PowerPCAsmPrinter -> PowerPCInfo PowerPCAsmPrinter -> Support PowerPCAsmPrinter -> System PowerPCAsmPrinter -> Target PowerPCCodeGen -> CodeGen PowerPCCodeGen -> Core PowerPCCo...

> Something like this should work: > > for (Module::iterator F = M->begin(), E = M->end(); F != E; ++F) > if (F->isExternal()) > ... Function* F is external! ... This is not working. For some reason there is a BasicBlock present on undefined functions ! I am compiling the examples from llvm/test/feature, about 28 out of 34 assemble fine. Just cannot seem to get

...l hours :( There are two types of external functions that the code generator deals with: external functions that are present in the LLVM program, and external functions used by the code generator. I suspect that you are hitting cases where the later are not getting printed. If you look at the PowerPCAsmPrinter.cpp it has to do very similar things to what you are doing. Note that it uses a "FnStubs" set to collect references to external functions as they are emitted. Once it builds this set, it emits a stub for each external function at the bottom of the file. I think you should do somethi...

>> If you take a look at the PowerPC asm printer, it has to do some special >> things for external functions as well, it might give you some ideas. > > I will have a look at this then. AFAICS there is nothing special here (PowerPCAsmPrinter.cpp). Aaron

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort

Hi David, Even if this works on Linux/ELF, do know whether it is "officially" supported? Using aliases to point to the interior of objects seems like something that could be very likely to break, but I don't know anything about how ELF encodes aliases. - Daniel On Tue, Aug 25, 2009 at 9:07 AM, David Chisnall<csdavec at swansea.ac.uk> wrote: > I've attached a