Hi Ian,
> On Mon, Feb 18, 2019 at 2:48 AM Rainer Orth <r...@cebitec.uni-bielefeld.de>
> wrote:
>>
>> > The code was already calling syscall, it was just doing it in a way
>> > that the types didn't necessarily match the C declaration. This is
>> > the implementation of Go's syscall.Syscall function, so there isn't
>> > really anything else we can do.
>>
>> I feared as much. Some time ago when debugging another issue I saw
>> libgo using syscall() directly, certainly unexpected in that particular
>> case.
>
> Those cases--where libgo calls syscall.Syscall--we can clean up where
> appropriate. What we can't clean up is user written Go code that
> calls syscall.Syscall directly.
I'll keep an eye open for the former when looking into the remaining Go
failures.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
