Mousius commented on PR #14179: URL: https://github.com/apache/tvm/pull/14179#issuecomment-1468569866
As with other compilers, ahead of time compilation can be applied to a much broader scope than just embedded and the graph executor does work in more constrained environments, is there any reason to limit AoT to just embedded scenarios? Considering a broader set of users, it makes sense to work from the interface, to the backend runtime we provide. If you have a user who starts out using the Graph executor, then decides to try using the C runtime, they'll suddenly find they've got an unwanted change in their application interface; as an end user, I would consider this unexpected behaviour and consider raising a bug given it impacted my application in a weird way. Having to link a different runtime by default (AOT infers C runtime) is also slightly irritating, but far less strange than a runtime change causing a users application to suddenly require changes. As an aside, the goal of reducing the number of arguments required is a good one, do we know which functions in the C++ runtime can't be implemented in the C runtime? If the C++ runtime was just a set of C wrappers the user wouldn't even need to choose? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
