Could it be possible to investigate why the kernel must use -mshort ?
Then we could see if we can fix that, to avoid requiring -mshort usage
at all.
The main reason is 16bit API everywhere you look -- not only TOS API itself but also XDD/XFS/XIF, XHDI etc APIs. So the solution would be to wrap syscalls (16bit -> 32bit wrapper) and then decide what to do with the rest, i.e. if we can live with loss of compatibility for older (closed source) modules or we will make wrapper for them, too. I remember my discussion with Frank about this topis, he had a very cool point -- what is such *big* advantage of getting rid of -mshort so I / you / anyone would invest such amount of time into it?
Btw Vincent, is there any way how to separate generation of mshort for libgcc and libstdc++ (and the others) ? Because as you have already pointed out, we need mshort for -lgcc link input but I see generation of all the others for -mshort as complete waste of (mine and CPU) time...
--