search for: msp430codegen

...CoreAsmPrinter -> XCoreInfo MSP430Info -> Support MSP430AsmPrinter -> AsmPrinter MSP430AsmPrinter -> CodeGen MSP430AsmPrinter -> Core MSP430AsmPrinter -> MC MSP430AsmPrinter -> MSP430Info MSP430AsmPrinter -> Support MSP430AsmPrinter -> System MSP430AsmPrinter -> Target MSP430CodeGen -> CodeGen MSP430CodeGen -> Core MSP430CodeGen -> MC MSP430CodeGen -> MSP430Info MSP430CodeGen -> SelectionDAG MSP430CodeGen -> Support MSP430CodeGen -> System MSP430CodeGen -> Target MipsInfo -> Support MipsAsmPrinter -> AsmPrinter MipsAsmPrinter -> CodeGen MipsAsm...

...e() lines). So I tracked this error down to where LLVM-Config.cmake is looking for targets whose name, given {target}, is either LLVM{target} or LLVM{target}CodeGen. Of course, I have no such targets. The weird thing is that I looked at the MSP430 directory, and it does not have LLVMMSP430 or LLVMMSP430CodeGen, either. It just has MSP430CodeGen yet somehow that target works just fine. *What am I missing?* Thanks! --Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171014/8935bf87/attachment.html>

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