This is the mail archive of the
mailing list for the GCC project.
Re: Go patch committed: Update libgo to 1.1.1
- From: Ian Lance Taylor <iant at google dot com>
- To: Uros Bizjak <ubizjak at gmail dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "gofrontend-dev at googlegroups dot com" <gofrontend-dev at googlegroups dot com>
- Date: Tue, 23 Jul 2013 15:23:04 -0700
- Subject: Re: Go patch committed: Update libgo to 1.1.1
- References: <CAFULd4bbzWxorBWTW=QbjbdNuWVC1Fi0M0H3hWXyrwdBNn53eg at mail dot gmail dot com>
On Mon, Jul 22, 2013 at 6:38 AM, Uros Bizjak <firstname.lastname@example.org> wrote:
>>>>>> I have committed a large patch to update libgo to the library that was
>>>>>> part of the Go 1.1.1 release. As usual, I'm not including the entire
>>>>>> patch in this e-mail message, because it is too large. I'm only
>>>>>> including the changes to the files that are partially gccgo-specific.
>>>>>> Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
>>>>>> Committed to mainline and 4.8 branch.
>>>>> I have hit following build failure on non-USING_SPLIT_STACK target
>>>> Thanks. Fixed like so. Committed to mainline and 4.8 branch.
>>> Thanks, with your patch, I was able to compile libgo without problems.
>>> The testsuite run exposes a timeout in net/http, I am looking into it.
> I have also managed to trigger the timeout on x86_64-pc-linux-gnu.
> The test was re-run with GOTESTFLAGS=--keep. When running the
> resulting a.out with "strace -f -o strace-x86_64 ./a.out" from the
> saved test directory, the test behaved in the same way as on alpha -
> it hever finished. I have attached the resulting trace (the test was
> killed with ctrl-c after some time).
Thanks. The problematic test is TestLinuxSendfile in
libgo/net/http/fs_test.go. That test binary invokes itself using
strace. In the trace here, that strace fails:
8511 ptrace(PTRACE_TRACEME, 0, 0, 0) = -1 EPERM (Operation not permitted)
8511 write(2, "strace: test_ptrace_setoptions_f"..., 96) = 96
The strace is supposed to start up a little server, and the test
binary tries to connect to that server. Since the server hasn't
started, the test times out.
The strace invocation is
strace -f -q -e trace=sendfile,sendfile64 ./a.out
Any idea why that would fail?
The Alpha stack trace you send also indicates a failure in this test.
It could be for the same reason; hard to say. The Alpha strace output
you send doesn't tell me much, since it wasn't done with -f.