From: Andreas Schwab <schwab@linux-m68k.org>
To: Ian Lance Taylor <iant@golang.org>
Cc: Ian Lance Taylor via Gcc-patches <gcc-patches@gcc.gnu.org>,
gofrontend-dev <gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Update to go1.15rc1
Date: Mon, 03 Aug 2020 19:28:48 +0200 [thread overview]
Message-ID: <874kpjprjj.fsf@igel.home> (raw)
In-Reply-To: <CAOyqgcVt4NkhjX_sqrYCGKF6+sV_Qjz3-pA1GLzDcjr0NqQkow@mail.gmail.com> (Ian Lance Taylor's message of "Mon, 3 Aug 2020 10:13:05 -0700")
On Aug 03 2020, Ian Lance Taylor wrote:
> On Sun, Aug 2, 2020 at 12:50 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>>
>> This breaks ia64-linux. According to
>> arch/ia64/kernel/syscalls/syscall.tbl, the getrandom syscall is 315 and
>> copy_file_range is 323.
>>
>> ../../../libgo/go/internal/syscall/unix/copy_file_range_linux.go:13:42: error: reference to undefined name 'copyFileRangeTrap'
>> 13 | r1, _, errno := syscall.Syscall6(copyFileRangeTrap,
>> | ^
>> ../../../libgo/go/internal/syscall/unix/getrandom_linux.go:35:41: error: reference to undefined name 'getrandomTrap'
>> 35 | r1, _, errno := syscall.Syscall(getrandomTrap,
>> | ^
>> make[4]: *** [internal/syscall/unix.lo] Error 1
>> make[4]: *** Waiting for unfinished jobs....
>
> Thanks. Fixed like so. Committed to mainline.
Actually, on ia64 syscall numbers are offset by 1024, thus the correct
numbers are 1339 and 1347.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-08-03 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 19:28 Ian Lance Taylor
2020-08-02 7:50 ` Andreas Schwab
2020-08-03 17:13 ` Ian Lance Taylor
2020-08-03 17:28 ` Andreas Schwab [this message]
2020-08-03 18:04 ` Ian Lance Taylor
2020-08-02 20:00 ` Rainer Orth
2020-08-04 17:21 ` Ian Lance Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kpjprjj.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).