cmd/7l: external linking support

Question

cmd/7l: external linking support

minux opened this issue 10 years ago · 4 comments

Answer 1 · 2015-02-19T08:23:00.000Z

Given I have my head in the linker currently, I could have a go at this. Do you think it's something that could be reasonably implemented given the current state of things, or would it be futile for the moment?

Answer 2 · 2015-02-19T08:26:35.000Z

I think it's reasonable to start implementing external linking at this stage. We're pretty close to all.bash passing.

Answer 3 · 2015-02-19T08:30:19.000Z

Actually, external linking development can start even earlier. Once you have a hello world program working, it could start. Just generate a go.o relocatable ELF and use ld to do the final linking. Once ld could produce working binary, it's mostly done. And then we will need cgo support.

Answer 4 · 2015-02-19T10:48:32.000Z

OK, I had a quick hack, see branch I pushed. Something goes wrong with the
dwarf relocs (and I don't understand the dwarf bits of the linker at all
yet) but it you pass -w it makes a binary. Which segfaults in osinit -
possibly just after the first syscall, although I don't know if that is
relevant. The fact that the smallest possible go program is quite large
strikes again - maybe I'll try with the mini runtime tomorrow.

sent from my phone, please excuse brevity
On 19 Feb 2015 21:30, "Minux Ma" notifications@github.com wrote:

Actually, external linking development can start even earlier.
Once you have a hello world program working, it could start.

Just generate a go.o relocatable ELF and use ld to do the final
linking. Once ld could produce working binary, it's mostly done.

And then we will need cgo support.

—
Reply to this email directly or view it on GitHub
https://github.com/4ad/go/issues/130#issuecomment-75014332.