> actually, I think I was thinking this too. gcc would be its own world > right down to the system call level. No ?a or ?l compatibility issues; > you don't use them. Convert gcc calling conventions to plan 9 calling > conventions at the kernel interface (I had to do stuff like this for Xen > ...) > > So, if gcc is driving gas and gld, then the only issue is generating > plan 9 a.out format. libbfd can be taught to do this.
David Hogan did exactly this. Sure, it uses an APE-like library, but if all you want is open/read/write/close, who cares? /n/sources/extra/gcc Russ
