- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Stack (0.16 sec)
-
doc/go_mem.html
<code>i = *p</code> just before <code>funcs[i]()</code>. A Go compiler must not, because the value of <code>*p</code> may have changed. (Instead, the compiler could spill <code>i</code> to the stack.) </p> <p> Not allowing a single write to write multiple values also means not using the memory where a local variable will be written as temporary storage before the write.
HTML - Registered: Tue Apr 16 11:13:10 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
doc/go1.22.html
<a href="/pkg/sync#RWMutex"><code>sync.RWMutex</code></a>. Contention on runtime-internal locks is always reported at <code>runtime._LostContendedRuntimeLock</code>. A future release will add complete stack traces in these cases. </p> <p><!-- https://go.dev/issue/50891 --> CPU profiles on Darwin platforms now contain the process's memory map, enabling the disassembly view in the pprof tool. </p>
HTML - Registered: Tue Feb 06 11:13:10 GMT 2024 - Last Modified: Wed Jan 31 20:51:56 GMT 2024 - 45.6K bytes - Viewed (0) -
doc/asm.html
function contains no call instructions. Otherwise, the local stack frame must not contain pointers, and the assembly must confirm this fact by executing the pseudo-instruction <code>NO_LOCAL_POINTERS</code>. Because stack resizing is implemented by moving the stack, the stack pointer may change during any function call: even pointers to stack data must not be kept in local variables. </p> <p>
HTML - Registered: Tue Apr 16 11:13:10 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0)