areusch commented on PR #12509: URL: https://github.com/apache/tvm/pull/12509#issuecomment-1232267099
for context for the Community Meeting tomorrow: `hexagon` is a backend which effectively compiles code in the same way as the LLVM target, but which at runtime needs a different Device API. At compile time, there's no reason that `hexagon` needs to use a different `target.build`. However, at present, we tie the runtime `device_type` to the Target `kind`. There are a few different options at least for how we could resolve this: 1. allow this PR through, which lets the user configure it. However, a user may not necessarily understand which device type to use, and there may exist cases where the target device type shouldn't be included in tuning logs. 2. leave device_type for hexagon to be `kDLCPU`, and override the CPU Device API via patching the `runtime::Registry`. 3. allow targets to be flexible in determining their device_type, and make `llvm -mcpu=hexagonvNN` choose `hexagon` as the device type. this avoids the need to patch the registry. -- 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]
