search for: nativetarget

...ble. For example: * Some executables only depend on the asm parsers and only call InitializeAllAsmParsers (similarly for any other All*) - see the various AllTargetsAsmParsers and similar rules in cmake/modules/LLVM-Config.cmake * Some executables depend only on the native target support InitializeNativeTarget* functions - see the JIT tests and the "native" and "nativecodegen" rules in the above cmake file. So... - any ideas? Should we just give up some of this fine grained dependency control & say you can only depend on all targets? (or maybe "all targets or the native targ...

...v Sent: Wednesday, December 06, 2017 5:14 PM To: Eric Christopher Cc: llvm-dev; Richard Smith Subject: Re: [llvm-dev] TargetSelect.h and layering FWIW, I think the end state we'll end up wanting is what you describe in your email: fine grained dependencies and something like libLLVM{AllTargets,NativeTarget}{AsmPrinters,AsmParsers,Descs,Disassemblers,Infos} I think the "Native" thing can be solved by having a CMake (and llvm-config) level alias that points to a specific single target library. Then I think you could actually build lib/Target/All/... directory tree that provides the "all...

My only alternate ideas are: a) To heck with this only a single target thing. b) Autogenerate the entire file and library support as part of the build and have the various functions "defined" in the appropriate libraries. I don't really think a) is feasible, and b) is a bit of a stretch too. :\ -eric On Mon, Dec 4, 2017 at 5:37 PM David Blaikie <dblaikie at gmail.com>