mirror of
https://github.com/golang/go
synced 2024-10-02 04:18:33 -06:00
5fea2ccc77
The tree's pretty inconsistent about single space vs double space after a period in documentation. Make it consistently a single space, per earlier decisions. This means contributors won't be confused by misleading precedence. This CL doesn't use go/doc to parse. It only addresses // comments. It was generated with: $ perl -i -npe 's,^(\s*// .+[a-z]\.) +([A-Z]),$1 $2,' $(git grep -l -E '^\s*//(.+\.) +([A-Z])') $ go test go/doc -update Change-Id: Iccdb99c37c797ef1f804a94b22ba5ee4b500c4f7 Reviewed-on: https://go-review.googlesource.com/20022 Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Dave Day <djd@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
26 lines
1023 B
C
26 lines
1023 B
C
// Copyright 2015 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.
|
|
|
|
// FIXED_FRAME defines the size of the fixed part of a stack frame. A stack
|
|
// frame looks like this:
|
|
//
|
|
// +---------------------+
|
|
// | local variable area |
|
|
// +---------------------+
|
|
// | argument area |
|
|
// +---------------------+ <- R1+FIXED_FRAME
|
|
// | fixed area |
|
|
// +---------------------+ <- R1
|
|
//
|
|
// So a function that sets up a stack frame at all uses as least FIXED_FRAME
|
|
// bytes of stack. This mostly affects assembly that calls other functions
|
|
// with arguments (the arguments should be stored at FIXED_FRAME+0(R1),
|
|
// FIXED_FRAME+8(R1) etc) and some other low-level places.
|
|
//
|
|
// The reason for using a constant is to make supporting PIC easier (although
|
|
// we only support PIC on ppc64le which has a minimum 32 bytes of stack frame,
|
|
// and currently always use that much, PIC on ppc64 would need to use 48).
|
|
|
|
#define FIXED_FRAME 32
|