That looks like something escaped to the heap. If you pass the -S option to the compiler, the assembly output will have the symbolic name of the type being allocated (at the LEAQ 2 instructions before the call to newobject). If you pass the -m option to the compiler, it will tell you what escaped and why.
On Wednesday, September 23, 2020 at 6:48:44 AM UTC-7 Jan Mercl wrote: > On Wed, Sep 23, 2020 at 3:36 PM 'ju...@sqreen.com' via golang-nuts > <golan...@googlegroups.com> wrote: > > > I was surprised to find a heap allocation in the following function > prolog: > > https://gist.github.com/Julio-Guerra/a3a2088832cd927669c08e1127e4c25a > > I think the function prolog consists of the first three assembler > instructions, with the possible additional prolog at 4fedf0 when stack > must be enlarged. > -- 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/950a3604-11e9-4998-a15d-122b1f6da909n%40googlegroups.com.
