[LLVMdev] [lld] lld build needs to have flags that specify what flavor/targets to build ? (original) (raw)
Alex Rosenberg alexr at leftfield.org
Wed Oct 8 11:45:45 PDT 2014
- Previous message: [LLVMdev] [lld] lld build needs to have flags that specify what flavor/targets to build ?
- Next message: [LLVMdev] [lld] lld build needs to have flags that specify what flavor/targets to build ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This it totally "armchair quarterbacking," but I am a little frustrated that we've come to conflate flavors and targets.
The original intent of flavors was to internally translate each flavor into a neutral lld-native command line syntax. We now have baked in assumptions of behavior based on flavor.
If I want to cross-compile from OS X for Windows PECOFF, I don't think it feels correct to use a LINK.EXE command line flavor from OS X and I'd rather use an lld-native flavor.
Alex
On Oct 7, 2014, at 2:22 PM, Shankar Easwaran <shankare at codeaurora.org> wrote:
On 10/7/2014 4:10 PM, Nick Kledzik wrote:
Shankar,
Can you give provide a scenario where you want this? I’m not sure what you want here. a) LLVM could be built just for one target(LLVMTARGETSTOBUILD) b) With LTO this case might happen more often, where an user would have compiled LLVM just for one architecture and lld would support other architectures that LLVM would not support. c) Printing all the targets/flavors that the linker currently supports. On Oct 7, 2014, at 2:03 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: Hi,
I think lld needs to have an infrastructure as part of the build process to build specific flavors and specific targets. This sounds like you want config-time choices (e.g. build a linker to only support ELF/x86 such as for a JIT). Yes. For this I was thinking that the Registry expand to consider flavors and targets that are part of the build process. So each flavor/target would register and the Driver would walk through the list of handlers to check if there is a handler defined for that flavor/target. This sounds like you want everything decided at runtime (e.g. all flavors registers all readers). Yes, right. Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
- Previous message: [LLVMdev] [lld] lld build needs to have flags that specify what flavor/targets to build ?
- Next message: [LLVMdev] [lld] lld build needs to have flags that specify what flavor/targets to build ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]