re python support. As with all TVM APIs, we will have first class python support in all of the proposals.
We are already using target triple for LLVM as part of the attribute, so it is mainly a question can be capture additional things. Or are we suggesting to increase the triple format?
To make better discussion, I would recommend everyone to give some examples of a target string that a user could write.
One thing to note on the hw side is that usually that will be more refined than a typical triple. For example, broadcom/bcm2711 could corresponds to a typical ARM triple that another device of cortex-a73 could corresponds to.
The main intention to introduce hardware is to allow most users avoid setting the attributes(e.g. mcpu) Because a hardware string usually implies all the information.
Alias
It is also interesting to ask about alias, broadcom/bcm2711 and broadcom/rasp4b could mean the same thing, but the later is more intuitive to the users.
Support Cloud Instance
Finally, we could ask if we want to include cloud instance as a type of hardware. aws/c4.xlarge is a prety useful flag that cloud users can directly use.
Support Multiple Device Choices
On certain devices, e.g. rockchip/rk3399, there are both GPU and CPUs, it would be useful to see if we can improve the hardware string to cover the choice of the device. for example rockchip/rk3399:gpu