**Scope of a Target**: Why do linker options belong to runtime configuration? Linking is a step in the module creation process, and it does affect the contents of the module. Are there any implicit assumption made about modules?
**Composite Target**: From the point of view of modularity, having a target host as a member of a composite target looks like a better solution. As the next step I suggest that we **drop the target host** completely. A function can be split into multiple parts meant for different targets. Instead of explicitly designating a certain target as a *target host*, we can use the same mechanism that assigns the individual parts to their targets to assign the "host" part to its target. This would remove the distinction between a host and a device code for the purposes of code generation. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-tvm-target-specification/6844/11) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/29a962bd40adf0be0d4f8ffda8b7a80b2a9d6b39415279952b3cad44eec9e554).
