To be clear, a fair amount of DWARF generation is already done in the compiler (bulk of the line table, subprogram DIEs and inline DIEs, debug ranges, etc).
As far as I know, there are no near term plans (at least within the compiler+runtime team) to work on moving other bits of DWARF generation to the compiler from the linker, but I don't think there would be any objection to someone else doing it. Than On Wed, Aug 19, 2020 at 11:21 AM Misha Gusarov <mi...@ridge.co> wrote: > Hello Than, > > Are there plans to implement remaining pieces (I'm interested > ing moving DWARF generation from linker to compiler) for 1.17, or is the > project considered done for now? > > Best, > Misha. > > On 18 Aug 2020, at 19:22, 'Than McIntosh' via golang-nuts wrote: > > > To add to what Ian mentioned: > > Many of the measures outlined in https://golang.org/s/better-linker have > been implemented at this point. It was a multi-person effort, several > members of the Go compiler/runtime team were involved (Jeremy, Cherry, > Austin, and myself). > > The new indexed object file format and the improved deadcode > implementation went into the tree in time to be included in Go 1.15. > > The additional changes in Go 1.16 include better streaming of data and > relocations from object file to linker output, a rewrite of the pclntab > code, support for content-addressable symbols, and more complete cleanup of > the old legacy linker data structures (e.g. removal of sym.Symbol). > > Some things mentioned in the doc that didn't get implemented include > moving to DWARF 5, and moving DWARF type generation from the linker to the > compiler. > > HTH. > > Cheers, Than > > On Sun, Aug 16, 2020 at 12:46 AM Ian Lance Taylor <i...@golang.org> wrote: > >> On Sat, Aug 15, 2020 at 11:49 AM Amnon <amno...@gmail.com> wrote: >> > >> > What is the best place to read about the ongoing work on the new linker? >> > With the Go 1.15 release, how far along are we with the plans? >> > What has been achieved? >> > And what is still to come? >> >> The work on the new linker is close to complete and has been merged >> into tip for the future 1.16 release (although 1.16 won't be released >> until next February). The work is as described at >> https://golang.org/s/better-linker. >> >> Ian >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXEK_OWZxKOUieHBdoH4R0eyddu_cMf_p_udWSKgZsHdA%40mail.gmail.com >> . >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CA%2BUr55EHRz5O3HvdP6xwOZyrHWKJA-Oc%2B96nMOCnB%3DmzABTYqA%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CA%2BUr55EHRz5O3HvdP6xwOZyrHWKJA-Oc%2B96nMOCnB%3DmzABTYqA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > Misha > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CA%2BUr55F9H3dk%2BV0asL8Mkjhx0ENWr%2BDBpoiW9ObhzTCaWNV3jw%40mail.gmail.com.
