> On 11 Feb 2019, at 22:32, Ramana Radhakrishnan <ramana....@googlemail.com>
> wrote:
> Can Olivier or someone who cares about vxworks also give this a quick
> sanity run for the alternate code path once we resolve some of the
> review questions here ? Don't we also need to worry about
> -mslow-flash-data where we get rid of literal pools and have movw /
> movt instructions ?
Thanks fo asking :)
I don't see obvious reasons why this would be problematic, but
you never know for sure until you try and I'll be happy to give
it a whirl on VxWorks.
I'll probably only be able to perform execution testing
on top of a gcc-8 toolchain though. I can also attempt
a VxWorks toolchain build with mainline of course.
Olivier
