On Thu, Jun 22, 2017 at 11:09 AM, Rainer Orth
wrote:
>
>> Because of how gccgo implements cgo calls, the code in dropm may not
>> have any write barriers. As a step toward implementing that, change
>> the gcstack, gcnextsegment, and gcnextsp fields of the g struct to
>> uintptr, so that assignmen
Hi Ian,
> Because of how gccgo implements cgo calls, the code in dropm may not
> have any write barriers. As a step toward implementing that, change
> the gcstack, gcnextsegment, and gcnextsp fields of the g struct to
> uintptr, so that assignments to them do not require write barriers.
> The gci
