search for: xcoreasmprint

...re -> Support Core -> System MCParser -> MC //MCParser -> Support MC -> Support //MC -> System Support -> System /* XCoreInfo -> Support XCore -> CodeGen XCore -> Core XCore -> MC XCore -> SelectionDAG XCore -> Support XCore -> Target XCore -> XCoreInfo XCoreAsmPrinter -> AsmPrinter XCoreAsmPrinter -> CodeGen XCoreAsmPrinter -> Core XCoreAsmPrinter -> MC XCoreAsmPrinter -> Support XCoreAsmPrinter -> System XCoreAsmPrinter -> Target XCoreAsmPrinter -> XCoreInfo MSP430Info -> Support MSP430AsmPrinter -> AsmPrinter MSP430AsmPrinter -&...

..., how can I change the way that my target > outputs globals variables? Ryan, On which version are you working? I can see, since r93858; Author: Chris Lattner <sabre at nondot.org> Date: Tue Jan 19 14:38:33 2010 + virtual void EmitGlobalVariable(const GlobalVariable *GV); It seems XCoreAsmPrinter overrides some methods. ...Takumi

I'm working on building a target for llvm that's the intermediate language of another compiler, so that the other compiler can benifit from llvm's optimization passes. I essentially made a copy of the mips backend, and then started changing the output to match the intermediate language of the compiler. Most of the output can be overriden, but I haven't figured out how to change

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