> Using a standard linker instead doesn't work well for

Question

> Using a standard linker instead doesn't work well for

a managed language. The Go runtime needs to know where all the pointers are in the data and bss segments, and a standard linker won't put that information together for you. The Go linker does that. The Go linker also writes out runtime information for unwinding stacks during GC and translating program counters to file:line for use in stack dumps. Again, this is all much easier to do with a toolchain that we control entirely than having to build into existing ones. (I am not aware of any way to get file:line information through an existing linker except in DWARF tables, which is overkill. And then there's OS X and Windows, where you _really_ have no control over the toolchain.)

(https://news.ycombinator.com/item?id=8817990)

#backend #go #programming #russian

0

08.12.2018

1 ответов

4 просмотра

Andrey · Accepted Answer

Andrey

а когда Го успел свой рантайм получить?

0

08.12.2018

170 похожих чатов

> Using a standard linker instead doesn't work well for

1 ответов

Похожие вопросы