Re: [PATCH v5 17/25] AArch64: Report tag violation error information

Simon Marchi via Gdb-patches
2021-02-05T16:13:21Z

> Right. This is being exposed so MI can potentially use the information (as is done for i386-linux). Though I wouldn't say it is guaranteed to be kept the same.
>
> Honestly, the goal is not to enable an MI MTE API right now. When the functionality is pushed and working well, then we can focus on making the MI layer MTE-aware.
>
> The new commands, for example, don't have MI counterparts at this point.
>
> Given only a handful of architectures are using tagged memory, I'm not even sure if it is worth coming up with an MI API yet.

I'm not talking about new MI commands, but MI output. If these fields
are emitted today (with this patch series), someone MI frontend could
read and make use of them, so they should be considered API and not
change (in a backwards-incompatible way) in the future. So we should at
least make sure that what this outputs does not paint us in a corner.

Simon