Honestly, I cannot imagine practical application of it. But I understand that
Go tries to cover the case.
Thank you for your answers.
Hiroshi
Sent with Unibox
> On Jul 20, 2017, at 2:40 AM, Ian Lance Taylor wrote:
>
>
> On Wed, Jul 19, 2017 at 2:10 AM, Hiroshi
Oh, I made a mistake. I mean shared => static/shared.
Sent with Unibox
> On Jul 19, 2017, at 6:10 PM, Hiroshi Ioka wrote:
>
>
> Thank you, I understand the situation mostly.
>
>
>> Before that change, newosproc0 was used when code built with
> -build
Thank you, I understand the situation mostly.
> Before that change, newosproc0 was used when code built with
-buildmode=c-archive did not use cgo.
Is there any use case for shared libraries that don’t have exported functions?
Hiroshi
Sent with Unibox
> On Jul 19, 2017, at 7:40 AM, Ian Lan
I see. Thanks.
Sent with Unibox
> On Jul 18, 2017, at 1:03 AM, Aram Hăvărneanu wrote:
>
>
>> nitpick. os3_solaris.go.go set stack size by itself, instead of
>> using default one. is it intentional?
>>
>
>
>
>
> You mean why does it explicitely ask for a 2MB stack when 2MB stacks
> ar
