Ian,
>>> I committed the libgo patch to the upstream repository.
>>
>> I completely missed that: at least in https://go.googlecode.com/hg/
>> libtool.m4 isn't present.
>
> The immediate upstream project for libgo is
> https://gofrontend.googlecode.com/hg/ . Most of the files in the libgo
> direct
Rainer Orth writes:
> Ian Lance Taylor writes:
>
>> Rainer Orth writes:
>>
>>> All bootstraps have completed without regressions, so I've installed the
>>> patch as is, after verifying that the libgo parts aren't present in the
>>> upstream Go repo.
>>
>> I committed the libgo patch to the upst
Ian Lance Taylor writes:
> Rainer Orth writes:
>
>> All bootstraps have completed without regressions, so I've installed the
>> patch as is, after verifying that the libgo parts aren't present in the
>> upstream Go repo.
>
> I committed the libgo patch to the upstream repository.
I completely m
Rainer Orth writes:
> All bootstraps have completed without regressions, so I've installed the
> patch as is, after verifying that the libgo parts aren't present in the
> upstream Go repo.
I committed the libgo patch to the upstream repository.
Thanks.
Ian
diff -r 70b5a35b2d19 libgo/config/li
Rainer Orth writes:
> There has long been some clamoring for a amd64-*-solaris2 configuration
> similar to sparcv9-sun-solaris2. I've resisted this for quite some
> time, primarily because it doubles the maintenance effort of testing
> both the 32-bit default and 64-bit default configurations.
[
> Thanks, I'll give it a try. I just seemd weird to have MASK_V8PLUS and
> MASK_V9 at the same time.
Yes, that's why the existing comment should also be enhanced. I'll fix it.
--
Eric Botcazou
Eric Botcazou writes:
>> * In the sparcv9-sun-solaris2.11 builds, the 32-bit libgo tests fail to
>> link since they have unresolved references to
>> __sync_bool_compare_and_swap_8 and __sync_add_and_fetch_8. I could
>> trace this to -mv8plus being missing in that configuration. I'm
>> u
> * In the sparcv9-sun-solaris2.11 builds, the 32-bit libgo tests fail to
> link since they have unresolved references to
> __sync_bool_compare_and_swap_8 and __sync_add_and_fetch_8. I could
> trace this to -mv8plus being missing in that configuration. I'm
> uncertain where best to handle
