On Fri, Oct 5, 2018 at 2:46 PM, Scott Cotton <w...@iri-labs.com> wrote: > > Do you have any more pointers about how one may assess whether or ensure > that a stack overflow check > is not necessary in order to safely use this directive?
You basically have to know what you're doing. In the general case, whether go:nosplit is safe is going to depend on details of compiler code generation that may vary from release to release. In practice, go:nosplit is safe enough for a leaf function that has no large local variables. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
