On Thu, 14 Nov 2019 at 17:47, Peter Maydell <peter.mayd...@linaro.org> wrote:
> The ARM semihosting ABI also has a number of warts > which are basically historical legacy. With a clean > sheet you get to avoid some of them. (Notably you could > skip the whole 'negotiate presence of extensions' business > by just getting those parts right from the start ...better still, if you can define (a) a mandatory "return version and feature bit info" call right from the start and (b) the required behaviour for attempts to make a semihosting call with an unknown/unimplemented function number -- then you can avoid the nasty kludge "magic behaviour by opening a magic filename" we were stuck with specifying in arm semihosting 2.0. thanks -- PMM
