-
Michael Hudson-Doyle authored
The long comment block in obj6.go:progedit talked about the two code sequences for accessing g as "local exec" and "initial exec", but really they are both forms of local exec. This stuff is confusing enough without using the wrong words for things, so rewrite it to talk about 2-instruction and 1-instruction sequences. Unfortunately the confusion has made it into code, with the R_TLS_IE relocation now doing double duty as meaning actual initial exec when externally linking and boring old local exec when linking internally (half of this is my fault). So this stops using R_TLS_IE in the local exec case. There is a chance this might break plan9 or windows, but I don't think so. Next step is working out what the heck is going on on ARM... Change-Id: I09da4388210cf49dbc99fd25f5172bbe517cee57 Reviewed-on: https://go-review.googlesource.com/9273Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org>
264858c4
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
arm | ||
arm64 | ||
ppc64 | ||
x86 | ||
ar.go | ||
data.go | ||
flag.go | ||
fmt.go | ||
funcdata.go | ||
go.go | ||
ld.go | ||
libc.go | ||
line_test.go | ||
link.go | ||
mgc0.go | ||
obj.go | ||
objfile.go | ||
pass.go | ||
pcln.go | ||
stack.go | ||
stringer.go | ||
sym.go | ||
textflag.go | ||
typekind.go | ||
util.go |