[9fans] Format for relocatable objects

2009-01-06 Thread lucio
Where should I look for the format of Plan 9 objects as created by the compiler(s) and ready for linking? I'm hoping there is a place other than the compiler sources that documents this intermediate format, which I presume is not totally unlike a.out. Also, while I'm asking, there must be more

Re: [9fans] Format for relocatable objects

2009-01-06 Thread Charles Forsyth
.[8kvq965] ... files are unrelated to a.out. as ken thompson's paper says The object files are binary forms of assembly language, similar to what might be passed between the first and second passes of an assembler. they contain target-dependent code but not precise

Re: [9fans] Format for relocatable objects

2009-01-06 Thread lucio
one nice thing about the scheme is that in the compiler suite only the loader knows or needs to know the bit patterns and peculiar properties of the actual machine. Thank you for reminding me, I thought I'd seen the details somewhere. Now to actually absorb them, given that if I were to read

Re: [9fans] Format for relocatable objects

2009-01-06 Thread erik quanstrom
It would be a shame (but no disaster) if Binutil's nm and other tools could not at least display native Plan 9 intermediate files. I need to know or decide how far to take this exercise. why would that be advantagous on plan 9? if you teach gcc to output, e.g., 8.out, then what is gained by

Re: [9fans] Format for relocatable objects

2009-01-06 Thread Charles Forsyth
Now to actually absorb them, given that if I were to read your comments literally, I'd assume that the intermediate code would be machine independent. not if you're reading my comments literally. i'd already observed that they contain target-dependent code but not precise machine instructions,

Re: [9fans] Format for relocatable objects

2009-01-06 Thread Roman V. Shaposhnik
On Tue, 2009-01-06 at 15:09 -0500, erik quanstrom wrote: It would be a shame (but no disaster) if Binutil's nm and other tools could not at least display native Plan 9 intermediate files. I need to know or decide how far to take this exercise. why would that be advantagous on plan 9?

Re: [9fans] Format for relocatable objects

2009-01-06 Thread erik quanstrom
On Tue, 2009-01-06 at 15:09 -0500, erik quanstrom wrote: It would be a shame (but no disaster) if Binutil's nm and other tools could not at least display native Plan 9 intermediate files. I need to know or decide how far to take this exercise. why would that be advantagous on plan 9?

Re: [9fans] Format for relocatable objects

2009-01-06 Thread Roman V. Shaposhnik
On Tue, 2009-01-06 at 17:54 -0500, erik quanstrom wrote: On Tue, 2009-01-06 at 15:09 -0500, erik quanstrom wrote: It would be a shame (but no disaster) if Binutil's nm and other tools could not at least display native Plan 9 intermediate files. I need to know or decide how far to take

Re: [9fans] Format for relocatable objects

2009-01-06 Thread lucio
Not *on* Plan9, but *for* Plan9: think cross-environment. I thought about that, but dismissed it because Plan 9 objects exist only in a Plan 9 environment in the scenario Erik envisages. But, funny enough, I am currently using NetBSD as my GCC platform, so your point is not entirely irrelevant.

Re: [9fans] Format for relocatable objects

2009-01-06 Thread lucio
Well, that's what I meant: binutils on Linux (or any other UNIX for that matter) understood Plan9's *.out files you can set up a cross-environment *on Linux* and deploy on Plan9. I'm not sure its a killer application, but its a use case. It's also a necessity in order to bootstrap the GCC