Audean Wiki - go:internals

All pages

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

All pages A * All pages * asm C * cdecl * Copyrights F * Front Page * FS G * G * get tls M * M N * Notes by MC S * split stacks * stdcall T * textflag * Third-party articles * Thread-local storage U * User statistics X * x86 calling conventions

asm

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

asm You can find some valuable information in the docs for the Plan 9 assembler, predecessor of the 8a/6a/5a assemblers. Some x86 assembly helpful links: * movs, rep, cld etc. * Intel's manual might also be interesting...

Copyrights

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

Copyrights All text in this wiki, except where otherwise stated, is: Copyright by "Go internals (unofficial) wiki" authors. and available on terms of the Creative Commons Attribution-ShareAlike license.

FS

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

FS FS is a register name in the x86 architecture. For its usage, see: Thread-local storage. It is a segment register, which means that the current setting of the segment descriptor table maps references to FS to some underlying RAM.

G

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

G Letter “g” -- is generally often used as a shorthand to a phrase “(current) goroutine” -- see: . Strictly related: * G (struct G) -- is an internal C struct containing some data related to a goroutine -- see: pkg/runtime/runtime.h * g (G g) -- is a thread-local variable of type

get tls

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

get tls get_tls(r) is an assembly macro for retrieving the location (address) of Thread-local storage (TLS is thus an acronym). It is defined in automatically generated (during Go building) file asm.h. For GOOS=386, get_tls(r) resolves to: MOVL 0x2c(FS), r See also

M

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

M Letter “m” -- is generally often used as a shorthand to a phrase (current) OS thread -- see: (link). Strictly related: * M (struct M) -- is an internal C struct containing some data related to an OS thread -- see: pkg/runtime/runtime.h * 'm' (M m) -- is a thread-local variable of type

Notes by MC

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

Notes by MC Links * * extern register * "callbacks" attempts ("Out-of-band callbacks with cgo") * other notes, probably related * blog entry on cgo callbacks, dated 24.04.2010. * CL 834045 - "Library support for cgo export". * introduces startcgocallback(), endcgocallback() in runtime/proc.c, cgocallback() in runtime/cgocall.c, runcgocallback()

split stacks

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

split stacks On Split Stacks in gcc wiki (link thanks to the jra's thoughts blog), by Ian Lance Taylor (one of the core Go developers). For additional details about implementation in Go, check the big blocks of comments in pkg/runtime/proc.c. A blog posting titled “A trip down the (split) rabbit hole

stdcall

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

stdcall See: x86 calling conventions. Note, that for WinAPI calls (and callbacks) on x86 the convention is stdcall.

textflag

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

textflag A flag for the “ld” linker, with special link-time information about a function. textflag 7 Extracted from a comment in pkg/runtime/proc.c: * Newproc and deferproc need to be textflag 7 * (no possible stack split when nearing overflow)

Third-party articles

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

Third-party articles (The articles are annotated with publication date. That's because Go internals change from time to time, so older writeups have higher risk of becoming obsolete with time.) * 2013.09.08 The Go netpoller. A short, high-level overview. * 2013.06.30

Thread-local storage

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

Thread-local storage See an explanation on Wikipedia and on MSDN. Additional notes: * In an x86 environment, the FS register points to the current value of the “Thread Information Block” (TIB) structure. (ref.),(ref.) * Wikipedia on TIB (Thread Information Block) / TEB (Thread Environment Block) * specifically, FS:0x2C - “

User statistics

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

User statistics (on the original wiki) User Edits Pages Created Files Contributed First Edit Date Last Edit Last Page Edited MateuszCzapliński 80 15 15 unknown 2014-01-10 15:27:10 Thirdparty articles tcnsc

x86 calling conventions

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Nov 2020 17:23:36 +0000

x86 calling conventions See: Wikipedia on cdecl, stdcall and other calling conventions]. Also highly informative: The history of calling conventions, part 1 and further parts. An extract from “libcgo/386.S” about the 8c/8a/8g calling convention: * Calling into the 8c tool chain, where all registers are caller save.