2013-08-31 10:32:07 -06:00
|
|
|
// Copyright 2009 The Go Authors. All rights reserved.
|
|
|
|
|
// Use of this source code is governed by a BSD-style
|
|
|
|
|
// license that can be found in the LICENSE file.
|
|
|
|
|
//
|
|
|
|
|
// System calls and other sys.stuff for 386, FreeBSD
|
|
|
|
|
// /usr/src/sys/kern/syscalls.master for syscall numbers.
|
|
|
|
|
//
|
|
|
|
|
|
[dev.cc] runtime: convert assembly files for C to Go transition
The main change is that #include "zasm_GOOS_GOARCH.h"
is now #include "go_asm.h" and/or #include "go_tls.h".
Also, because C StackGuard is now Go _StackGuard,
the assembly name changes from const_StackGuard to
const__StackGuard.
In asm_$GOARCH.s, add new function getg, formerly
implemented in C.
The renamed atomics now have Go wrappers, to get
escape analysis annotations right. Those wrappers
are in CL 174860043.
LGTM=r, aram
R=r, aram
CC=austin, dvyukov, golang-codereviews, iant, khr
https://golang.org/cl/168510043
2014-11-11 15:06:22 -07:00
|
|
|
#include "go_asm.h"
|
|
|
|
|
#include "go_tls.h"
|
2014-09-04 21:05:18 -06:00
|
|
|
#include "textflag.h"
|
2013-08-31 10:32:07 -06:00
|
|
|
|
|
|
|
|
TEXT runtime·sys_umtx_sleep(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $469, AX // umtx_sleep
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
NEGL AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+12(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sys_umtx_wakeup(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $470, AX // umtx_wakeup
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
NEGL AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+8(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·lwp_create(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $495, AX // lwp_create
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+4(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·lwp_start(SB),NOSPLIT,$0
|
|
|
|
|
|
|
|
|
|
// Set GS to point at m->tls.
|
|
|
|
|
MOVL mm+0(FP), BX
|
|
|
|
|
MOVL m_g0(BX), DX
|
|
|
|
|
LEAL m_tls(BX), BP
|
|
|
|
|
PUSHAL
|
|
|
|
|
PUSHL BP
|
|
|
|
|
CALL runtime·settls(SB)
|
|
|
|
|
POPL AX
|
|
|
|
|
POPAL
|
|
|
|
|
|
|
|
|
|
// Now segment is established. Initialize m, g.
|
|
|
|
|
get_tls(CX)
|
all: remove 'extern register M *m' from runtime
The runtime has historically held two dedicated values g (current goroutine)
and m (current thread) in 'extern register' slots (TLS on x86, real registers
backed by TLS on ARM).
This CL removes the extern register m; code now uses g->m.
On ARM, this frees up the register that formerly held m (R9).
This is important for NaCl, because NaCl ARM code cannot use R9 at all.
The Go 1 macrobenchmarks (those with per-op times >= 10 µs) are unaffected:
BenchmarkBinaryTree17 5491374955 5471024381 -0.37%
BenchmarkFannkuch11 4357101311 4275174828 -1.88%
BenchmarkGobDecode 11029957 11364184 +3.03%
BenchmarkGobEncode 6852205 6784822 -0.98%
BenchmarkGzip 650795967 650152275 -0.10%
BenchmarkGunzip 140962363 141041670 +0.06%
BenchmarkHTTPClientServer 71581 73081 +2.10%
BenchmarkJSONEncode 31928079 31913356 -0.05%
BenchmarkJSONDecode 117470065 113689916 -3.22%
BenchmarkMandelbrot200 6008923 5998712 -0.17%
BenchmarkGoParse 6310917 6327487 +0.26%
BenchmarkRegexpMatchMedium_1K 114568 114763 +0.17%
BenchmarkRegexpMatchHard_1K 168977 169244 +0.16%
BenchmarkRevcomp 935294971 914060918 -2.27%
BenchmarkTemplate 145917123 148186096 +1.55%
Minux previous reported larger variations, but these were caused by
run-to-run noise, not repeatable slowdowns.
Actual code changes by Minux.
I only did the docs and the benchmarking.
LGTM=dvyukov, iant, minux
R=minux, josharian, iant, dave, bradfitz, dvyukov
CC=golang-codereviews
https://golang.org/cl/109050043
2014-06-26 09:54:39 -06:00
|
|
|
MOVL BX, g_m(DX)
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL DX, g(CX)
|
|
|
|
|
|
|
|
|
|
CALL runtime·stackcheck(SB) // smashes AX, CX
|
|
|
|
|
MOVL 0(DX), DX // paranoia; check they are not nil
|
|
|
|
|
MOVL 0(BX), BX
|
|
|
|
|
|
|
|
|
|
// More paranoia; check that stack splitting code works.
|
|
|
|
|
PUSHAL
|
|
|
|
|
CALL runtime·emptyfunc(SB)
|
|
|
|
|
POPAL
|
|
|
|
|
|
|
|
|
|
CALL runtime·mstart(SB)
|
|
|
|
|
|
|
|
|
|
CALL runtime·exit1(SB)
|
|
|
|
|
MOVL $0x1234, 0x1005
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// Exit the entire program (like C exit)
|
|
|
|
|
TEXT runtime·exit(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $1, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·exit1(SB),NOSPLIT,$16
|
|
|
|
|
MOVL $0, 0(SP) // syscall gap
|
|
|
|
|
MOVL $0x10000, 4(SP) // arg 1 - how (EXTEXIT_LWP)
|
|
|
|
|
MOVL $0, 8(SP) // arg 2 - status
|
|
|
|
|
MOVL $0, 12(SP) // arg 3 - addr
|
|
|
|
|
MOVL $494, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·open(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $5, AX
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+12(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·close(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $6, AX
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+4(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·read(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $3, AX
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+12(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·write(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $4, AX
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+12(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·getrlimit(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $194, AX
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+8(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·raise(SB),NOSPLIT,$16
|
|
|
|
|
MOVL $496, AX // lwp_gettid
|
|
|
|
|
INT $0x80
|
|
|
|
|
MOVL $0, 0(SP)
|
|
|
|
|
MOVL $-1, 4(SP) // arg 1 - pid
|
|
|
|
|
MOVL AX, 8(SP) // arg 2 - tid
|
|
|
|
|
MOVL sig+0(FP), AX
|
|
|
|
|
MOVL AX, 8(SP) // arg 3 - signum
|
|
|
|
|
MOVL $497, AX // lwp_kill
|
|
|
|
|
INT $0x80
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·mmap(SB),NOSPLIT,$36
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
LEAL addr+0(FP), SI
|
2013-08-31 10:32:07 -06:00
|
|
|
LEAL 4(SP), DI
|
|
|
|
|
CLD
|
|
|
|
|
MOVSL // arg 1 - addr
|
|
|
|
|
MOVSL // arg 2 - len
|
|
|
|
|
MOVSL // arg 3 - prot
|
|
|
|
|
MOVSL // arg 4 - flags
|
|
|
|
|
MOVSL // arg 5 - fd
|
|
|
|
|
MOVL $0, AX
|
|
|
|
|
STOSL // arg 6 - pad
|
|
|
|
|
MOVSL // arg 7 - offset
|
|
|
|
|
MOVL $0, AX // top 32 bits of file offset
|
|
|
|
|
STOSL
|
|
|
|
|
MOVL $197, AX // sys_mmap
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+24(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·munmap(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $73, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·madvise(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $75, AX // madvise
|
|
|
|
|
INT $0x80
|
|
|
|
|
// ignore failure - maybe pages are locked
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·setitimer(SB), NOSPLIT, $-4
|
|
|
|
|
MOVL $83, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// func now() (sec int64, nsec int32)
|
|
|
|
|
TEXT time·now(SB), NOSPLIT, $32
|
|
|
|
|
MOVL $232, AX
|
|
|
|
|
LEAL 12(SP), BX
|
2014-02-26 21:15:34 -07:00
|
|
|
MOVL $0, 4(SP) // CLOCK_REALTIME
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL BX, 8(SP)
|
|
|
|
|
INT $0x80
|
|
|
|
|
MOVL 12(SP), AX // sec
|
|
|
|
|
MOVL 16(SP), BX // nsec
|
|
|
|
|
|
|
|
|
|
// sec is in AX, nsec in BX
|
|
|
|
|
MOVL AX, sec+0(FP)
|
|
|
|
|
MOVL $0, sec+4(FP)
|
|
|
|
|
MOVL BX, nsec+8(FP)
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// int64 nanotime(void) so really
|
|
|
|
|
// void nanotime(int64 *nsec)
|
|
|
|
|
TEXT runtime·nanotime(SB), NOSPLIT, $32
|
|
|
|
|
MOVL $232, AX
|
|
|
|
|
LEAL 12(SP), BX
|
2014-02-26 21:15:34 -07:00
|
|
|
MOVL $4, 4(SP) // CLOCK_MONOTONIC
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL BX, 8(SP)
|
|
|
|
|
INT $0x80
|
|
|
|
|
MOVL 12(SP), AX // sec
|
|
|
|
|
MOVL 16(SP), BX // nsec
|
|
|
|
|
|
|
|
|
|
// sec is in AX, nsec in BX
|
|
|
|
|
// convert to DX:AX nsec
|
|
|
|
|
MOVL $1000000000, CX
|
|
|
|
|
MULL CX
|
|
|
|
|
ADDL BX, AX
|
|
|
|
|
ADCL $0, DX
|
|
|
|
|
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret_lo+0(FP)
|
|
|
|
|
MOVL DX, ret_hi+4(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sigaction(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $342, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sigtramp(SB),NOSPLIT,$44
|
|
|
|
|
get_tls(CX)
|
|
|
|
|
|
all: remove 'extern register M *m' from runtime
The runtime has historically held two dedicated values g (current goroutine)
and m (current thread) in 'extern register' slots (TLS on x86, real registers
backed by TLS on ARM).
This CL removes the extern register m; code now uses g->m.
On ARM, this frees up the register that formerly held m (R9).
This is important for NaCl, because NaCl ARM code cannot use R9 at all.
The Go 1 macrobenchmarks (those with per-op times >= 10 µs) are unaffected:
BenchmarkBinaryTree17 5491374955 5471024381 -0.37%
BenchmarkFannkuch11 4357101311 4275174828 -1.88%
BenchmarkGobDecode 11029957 11364184 +3.03%
BenchmarkGobEncode 6852205 6784822 -0.98%
BenchmarkGzip 650795967 650152275 -0.10%
BenchmarkGunzip 140962363 141041670 +0.06%
BenchmarkHTTPClientServer 71581 73081 +2.10%
BenchmarkJSONEncode 31928079 31913356 -0.05%
BenchmarkJSONDecode 117470065 113689916 -3.22%
BenchmarkMandelbrot200 6008923 5998712 -0.17%
BenchmarkGoParse 6310917 6327487 +0.26%
BenchmarkRegexpMatchMedium_1K 114568 114763 +0.17%
BenchmarkRegexpMatchHard_1K 168977 169244 +0.16%
BenchmarkRevcomp 935294971 914060918 -2.27%
BenchmarkTemplate 145917123 148186096 +1.55%
Minux previous reported larger variations, but these were caused by
run-to-run noise, not repeatable slowdowns.
Actual code changes by Minux.
I only did the docs and the benchmarking.
LGTM=dvyukov, iant, minux
R=minux, josharian, iant, dave, bradfitz, dvyukov
CC=golang-codereviews
https://golang.org/cl/109050043
2014-06-26 09:54:39 -06:00
|
|
|
// check that g exists
|
|
|
|
|
MOVL g(CX), DI
|
|
|
|
|
CMPL DI, $0
|
2013-08-31 10:32:07 -06:00
|
|
|
JNE 6(PC)
|
|
|
|
|
MOVL signo+0(FP), BX
|
|
|
|
|
MOVL BX, 0(SP)
|
|
|
|
|
MOVL $runtime·badsignal(SB), AX
|
|
|
|
|
CALL AX
|
[dev.power64] cmd/5a, cmd/6a, cmd/8a, cmd/9a: make labels function-scoped
I removed support for jumping between functions years ago,
as part of doing the instruction layout for each function separately.
Given that, it makes sense to treat labels as function-scoped.
This lets each function have its own 'loop' label, for example.
Makes the assembly much cleaner and removes the last
reason anyone would reach for the 123(PC) form instead.
Note that this is on the dev.power64 branch, but it changes all
the assemblers. The change will ship in Go 1.5 (perhaps after
being ported into the new assembler).
Came up as part of CL 167730043.
LGTM=r
R=r
CC=austin, dave, golang-codereviews, minux
https://golang.org/cl/159670043
2014-10-28 19:50:16 -06:00
|
|
|
JMP ret
|
2013-08-31 10:32:07 -06:00
|
|
|
|
|
|
|
|
// save g
|
|
|
|
|
MOVL DI, 20(SP)
|
|
|
|
|
|
|
|
|
|
// g = m->gsignal
|
all: remove 'extern register M *m' from runtime
The runtime has historically held two dedicated values g (current goroutine)
and m (current thread) in 'extern register' slots (TLS on x86, real registers
backed by TLS on ARM).
This CL removes the extern register m; code now uses g->m.
On ARM, this frees up the register that formerly held m (R9).
This is important for NaCl, because NaCl ARM code cannot use R9 at all.
The Go 1 macrobenchmarks (those with per-op times >= 10 µs) are unaffected:
BenchmarkBinaryTree17 5491374955 5471024381 -0.37%
BenchmarkFannkuch11 4357101311 4275174828 -1.88%
BenchmarkGobDecode 11029957 11364184 +3.03%
BenchmarkGobEncode 6852205 6784822 -0.98%
BenchmarkGzip 650795967 650152275 -0.10%
BenchmarkGunzip 140962363 141041670 +0.06%
BenchmarkHTTPClientServer 71581 73081 +2.10%
BenchmarkJSONEncode 31928079 31913356 -0.05%
BenchmarkJSONDecode 117470065 113689916 -3.22%
BenchmarkMandelbrot200 6008923 5998712 -0.17%
BenchmarkGoParse 6310917 6327487 +0.26%
BenchmarkRegexpMatchMedium_1K 114568 114763 +0.17%
BenchmarkRegexpMatchHard_1K 168977 169244 +0.16%
BenchmarkRevcomp 935294971 914060918 -2.27%
BenchmarkTemplate 145917123 148186096 +1.55%
Minux previous reported larger variations, but these were caused by
run-to-run noise, not repeatable slowdowns.
Actual code changes by Minux.
I only did the docs and the benchmarking.
LGTM=dvyukov, iant, minux
R=minux, josharian, iant, dave, bradfitz, dvyukov
CC=golang-codereviews
https://golang.org/cl/109050043
2014-06-26 09:54:39 -06:00
|
|
|
MOVL g_m(DI), BX
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL m_gsignal(BX), BX
|
|
|
|
|
MOVL BX, g(CX)
|
|
|
|
|
|
|
|
|
|
// copy arguments for call to sighandler
|
|
|
|
|
MOVL signo+0(FP), BX
|
|
|
|
|
MOVL BX, 0(SP)
|
|
|
|
|
MOVL info+4(FP), BX
|
|
|
|
|
MOVL BX, 4(SP)
|
|
|
|
|
MOVL context+8(FP), BX
|
|
|
|
|
MOVL BX, 8(SP)
|
|
|
|
|
MOVL DI, 12(SP)
|
|
|
|
|
|
|
|
|
|
CALL runtime·sighandler(SB)
|
|
|
|
|
|
|
|
|
|
// restore g
|
|
|
|
|
get_tls(CX)
|
|
|
|
|
MOVL 20(SP), BX
|
|
|
|
|
MOVL BX, g(CX)
|
|
|
|
|
|
[dev.power64] cmd/5a, cmd/6a, cmd/8a, cmd/9a: make labels function-scoped
I removed support for jumping between functions years ago,
as part of doing the instruction layout for each function separately.
Given that, it makes sense to treat labels as function-scoped.
This lets each function have its own 'loop' label, for example.
Makes the assembly much cleaner and removes the last
reason anyone would reach for the 123(PC) form instead.
Note that this is on the dev.power64 branch, but it changes all
the assemblers. The change will ship in Go 1.5 (perhaps after
being ported into the new assembler).
Came up as part of CL 167730043.
LGTM=r
R=r
CC=austin, dave, golang-codereviews, minux
https://golang.org/cl/159670043
2014-10-28 19:50:16 -06:00
|
|
|
ret:
|
2013-08-31 10:32:07 -06:00
|
|
|
// call sigreturn
|
|
|
|
|
MOVL context+8(FP), AX
|
|
|
|
|
MOVL $0, 0(SP) // syscall gap
|
|
|
|
|
MOVL AX, 4(SP)
|
|
|
|
|
MOVL $344, AX // sigreturn(ucontext)
|
|
|
|
|
INT $0x80
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sigaltstack(SB),NOSPLIT,$0
|
|
|
|
|
MOVL $53, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·usleep(SB),NOSPLIT,$20
|
|
|
|
|
MOVL $0, DX
|
|
|
|
|
MOVL usec+0(FP), AX
|
|
|
|
|
MOVL $1000000, CX
|
|
|
|
|
DIVL CX
|
|
|
|
|
MOVL AX, 12(SP) // tv_sec
|
|
|
|
|
MOVL $1000, AX
|
|
|
|
|
MULL DX
|
|
|
|
|
MOVL AX, 16(SP) // tv_nsec
|
|
|
|
|
|
|
|
|
|
MOVL $0, 0(SP)
|
|
|
|
|
LEAL 12(SP), AX
|
|
|
|
|
MOVL AX, 4(SP) // arg 1 - rqtp
|
|
|
|
|
MOVL $0, 8(SP) // arg 2 - rmtp
|
|
|
|
|
MOVL $240, AX // sys_nanosleep
|
|
|
|
|
INT $0x80
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·setldt(SB),NOSPLIT,$4
|
|
|
|
|
// Under DragonFly we set the GS base instead of messing with the LDT.
|
|
|
|
|
MOVL tls0+4(FP), AX
|
|
|
|
|
MOVL AX, 0(SP)
|
|
|
|
|
CALL runtime·settls(SB)
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·settls(SB),NOSPLIT,$24
|
|
|
|
|
// adjust for ELF: wants to use -8(GS) and -4(GS) for g and m
|
|
|
|
|
MOVL tlsbase+0(FP), CX
|
|
|
|
|
ADDL $8, CX
|
|
|
|
|
|
|
|
|
|
// Set up a struct tls_info - a size of -1 maps the whole address
|
|
|
|
|
// space and is required for direct-tls access of variable data
|
|
|
|
|
// via negative offsets.
|
|
|
|
|
LEAL 16(SP), BX
|
|
|
|
|
MOVL CX, 16(SP) // base
|
|
|
|
|
MOVL $-1, 20(SP) // size
|
|
|
|
|
|
|
|
|
|
// set_tls_area returns the descriptor that needs to be loaded into GS.
|
|
|
|
|
MOVL $0, 0(SP) // syscall gap
|
|
|
|
|
MOVL $0, 4(SP) // arg 1 - which
|
|
|
|
|
MOVL BX, 8(SP) // arg 2 - tls_info
|
|
|
|
|
MOVL $8, 12(SP) // arg 3 - infosize
|
|
|
|
|
MOVL $472, AX // set_tls_area
|
|
|
|
|
INT $0x80
|
|
|
|
|
JCC 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
MOVW AX, GS
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sysctl(SB),NOSPLIT,$28
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
LEAL mib+0(FP), SI
|
2013-08-31 10:32:07 -06:00
|
|
|
LEAL 4(SP), DI
|
|
|
|
|
CLD
|
|
|
|
|
MOVSL // arg 1 - name
|
|
|
|
|
MOVSL // arg 2 - namelen
|
|
|
|
|
MOVSL // arg 3 - oldp
|
|
|
|
|
MOVSL // arg 4 - oldlenp
|
|
|
|
|
MOVSL // arg 5 - newp
|
|
|
|
|
MOVSL // arg 6 - newlen
|
|
|
|
|
MOVL $202, AX // sys___sysctl
|
|
|
|
|
INT $0x80
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
JCC 4(PC)
|
2013-08-31 10:32:07 -06:00
|
|
|
NEGL AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+24(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
MOVL $0, AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+24(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·osyield(SB),NOSPLIT,$-4
|
|
|
|
|
MOVL $331, AX // sys_sched_yield
|
|
|
|
|
INT $0x80
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
TEXT runtime·sigprocmask(SB),NOSPLIT,$16
|
|
|
|
|
MOVL $0, 0(SP) // syscall gap
|
|
|
|
|
MOVL $3, 4(SP) // arg 1 - how (SIG_SETMASK)
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL new+0(FP), AX
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL AX, 8(SP) // arg 2 - set
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL old+4(FP), AX
|
2013-08-31 10:32:07 -06:00
|
|
|
MOVL AX, 12(SP) // arg 3 - oset
|
|
|
|
|
MOVL $340, AX // sys_sigprocmask
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
MOVL $0xf1, 0xf1 // crash
|
|
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// int32 runtime·kqueue(void);
|
|
|
|
|
TEXT runtime·kqueue(SB),NOSPLIT,$0
|
|
|
|
|
MOVL $362, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
NEGL AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+0(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// int32 runtime·kevent(int kq, Kevent *changelist, int nchanges, Kevent *eventlist, int nevents, Timespec *timeout);
|
|
|
|
|
TEXT runtime·kevent(SB),NOSPLIT,$0
|
|
|
|
|
MOVL $363, AX
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
NEGL AX
|
cmd/cc, runtime: convert C compilers to use Go calling convention
To date, the C compilers and Go compilers differed only in how
values were returned from functions. This made it difficult to call
Go from C or C from Go if return values were involved. It also made
assembly called from Go and assembly called from C different.
This CL changes the C compiler to use the Go conventions, passing
results on the stack, after the arguments.
[Exception: this does not apply to C ... functions, because you can't
know where on the stack the arguments end.]
By doing this, the CL makes it possible to rewrite C functions into Go
one at a time, without worrying about which languages call that
function or which languages it calls.
This CL also updates all the assembly files in package runtime to use
the new conventions. Argument references of the form 40(SP) have
been rewritten to the form name+10(FP) instead, and there are now
Go func prototypes for every assembly function called from C or Go.
This means that 'go vet runtime' checks effectively every assembly
function, and go vet's output was used to automate the bulk of the
conversion.
Some functions, like seek and nsec on Plan 9, needed to be rewritten.
Many assembly routines called from C were reading arguments
incorrectly, using MOVL instead of MOVQ or vice versa, especially on
the less used systems like openbsd.
These were found by go vet and have been corrected too.
If we're lucky, this may reduce flakiness on those systems.
Tested on:
darwin/386
darwin/amd64
linux/arm
linux/386
linux/amd64
If this breaks another system, the bug is almost certainly in the
sys_$GOOS_$GOARCH.s file, since the rest of the CL is tested
by the combination of the above systems.
LGTM=dvyukov, iant
R=golang-codereviews, 0intro, dave, alex.brainman, dvyukov, iant
CC=golang-codereviews, josharian, r
https://golang.org/cl/135830043
2014-08-27 09:32:17 -06:00
|
|
|
MOVL AX, ret+24(FP)
|
2013-08-31 10:32:07 -06:00
|
|
|
RET
|
|
|
|
|
|
|
|
|
|
// int32 runtime·closeonexec(int32 fd);
|
|
|
|
|
TEXT runtime·closeonexec(SB),NOSPLIT,$32
|
|
|
|
|
MOVL $92, AX // fcntl
|
|
|
|
|
// 0(SP) is where the caller PC would be; kernel skips it
|
|
|
|
|
MOVL fd+0(FP), BX
|
|
|
|
|
MOVL BX, 4(SP) // fd
|
|
|
|
|
MOVL $2, 8(SP) // F_SETFD
|
|
|
|
|
MOVL $1, 12(SP) // FD_CLOEXEC
|
|
|
|
|
INT $0x80
|
|
|
|
|
JAE 2(PC)
|
|
|
|
|
NEGL AX
|
|
|
|
|
RET
|
|
|
|
|
|
2014-09-24 17:04:06 -06:00
|
|
|
GLOBL runtime·tlsoffset(SB),NOPTR,$4
|
