Independent from the engineering discussion. It would be useful to come back to the terminology and think about the UX consequence present that to the user. Obviously this is subjective, but worth to think about what can serve as a good story. I tried to search the term "Target" and "compiler target" on internet and here are some common interpretations:
- Target platform that the output runs on. - Target program that we outputs. "target platform" roughly aligns the first impression that comes up in my mind. A "platform" includes runtime libraries, hardwares, or any env that might affect the transformation behavior. Looking from that angle, "aws/c5" is certainly also a "target platform". A SoC with multiple chipsets, NPU, CPU can also certainly be viewed as a "target platform". A set of distributed machines can also be viewed as "target platform". So then it goes back to what stories we tell our users(affects developers as well), and whether or not that story aligns with the most common sense impressions. First kind of story: - S0a: A target is specifies the "target platform", any deployment environment constraints that you are interested. - S0b: If you are interested in multiple device settings, you can use a MultiTarget kind that composes up targets together and specifies the deployment env(that involves multiple devices). Second kind of story: - S1: A target is specifies the single device deployment constraints, you will need to compose them up to form a config, that also specifies the runtime and executor of your model. S0 ties back to the common sense stories with a progression(first start with only target on single device, simple and easily receptive, then generalize by reusing the same concept that aligns). S1 would require more understanding in differentiating the concept, and resolving confusion that why a SoC with multiple chipset is not a "target platform". --- [Visit Topic](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372/30) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/b69ff9064589ff473671b9dfe45dce8e4b4c60440a1af9ac8c9f65f95c346e2c).
