From: Ian Lance Taylor <iant@golang.org>
To: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: Re: [gofrontend-dev] [PATCH, go]: S/390: Fix generation of PtraceRegs
Date: Tue, 27 Jun 2017 21:51:00 -0000 [thread overview]
Message-ID: <CAOyqgcWZamUw1tfdm5auxL6ULAgpvZZPGb_fHKBWskqPf9Dsvg@mail.gmail.com> (raw)
In-Reply-To: <0f1319c4-e896-ae22-3a5d-c563a5292d8c@linux.vnet.ibm.com>
On Tue, Jun 27, 2017 at 12:52 AM, Andreas Krebbel
<krebbel@linux.vnet.ibm.com> wrote:
>
> go bootstrap fails on s390x starting with r249472. With including the ptrace header the s390 special
> code in mksysinfo.sh isn't used anymore:
>
> if test "$regs" = ""; then
> # s390
> regs=`grep '^type __user_regs_struct struct' gen-sysinfo.go || true`
> if test "$regs" != ""; then
> # Substructures of __user_regs_struct on s390
> upcase_fields "__user_psw_struct" "PtracePsw" >> ${OUT} || true
> upcase_fields "__user_fpregs_struct" "PtraceFpregs" >> ${OUT} || true
> upcase_fields "__user_per_struct" "PtracePer" >> ${OUT} || true
> fi
> fi
>
> Instead we fall through to the code with the generic handling which appears to work fine. The only
> difference is that the former code used to uppercase the initial letters of the struct member while
> the generic handler doesn't. The only user however appear to be syscall_linux_s390(x).go.
>
> The attached patch removes the mksysino.sh S/390 specific handling and adjusts the
> syscall_linux_s390* file accordingly.
>
> This fixes the bootstrap on s390x.
Thanks for sending this.
Committed to mainline.
Ian
prev parent reply other threads:[~2017-06-27 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 7:52 Andreas Krebbel
2017-06-27 21:51 ` Ian Lance Taylor [this message]
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=CAOyqgcWZamUw1tfdm5auxL6ULAgpvZZPGb_fHKBWskqPf9Dsvg@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=krebbel@linux.vnet.ibm.com \
/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).