• Russ Cox's avatar
    [dev.cc] liblink: disable GOOBJ=2 default · 2ecefd41
    Russ Cox authored
    The point of GOOBJ=2 was to have an active test of the cmd/internal/obj code.
    Now we have end-to-end tests of the assembler, and soon the compiler,
    so we don't need this halfway test on by default anymore.
    (It's still possible to enable during debugging with the
    environment variable.)
    
    The problem it causes on the builders is that this particular testing
    mode ends up with both the C process and the Go objwriter subprocess
    having the same very large Prog list in memory simultaneously,
    which causes basically a 2x memory blowup. In large programs
    (such as the one generated by test/rotate.go) this is significant.
    
    Disabling GOOBJ=2 should help with the current dev.cc builder
    failures.
    
    Change-Id: I1b11e4f29ea575659f02d2234242a904f7c867e4
    Reviewed-on: https://go-review.googlesource.com/4832
    Run-TryBot: Russ Cox <rsc@golang.org>
    Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
    2ecefd41
Name
Last commit
Last update
..
Makefile Loading commit data...
asm5.c Loading commit data...
asm6.c Loading commit data...
asm8.c Loading commit data...
asm9.c Loading commit data...
data.c Loading commit data...
go.c Loading commit data...
ld.c Loading commit data...
list5.c Loading commit data...
list6.c Loading commit data...
list8.c Loading commit data...
list9.c Loading commit data...
obj.c Loading commit data...
obj5.c Loading commit data...
obj6.c Loading commit data...
obj8.c Loading commit data...
obj9.c Loading commit data...
objfile.c Loading commit data...
objfilego.c Loading commit data...
pass.c Loading commit data...
pcln.c Loading commit data...
sym.c Loading commit data...