From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Ian Taylor <iant@golang.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: [PATCH, alpha, go]: Remove PtraceRegs definition to restore bootstrap
Date: Mon, 26 Jun 2017 07:24:00 -0000 [thread overview]
Message-ID: <CAFULd4bkZ4v6YziJPgRxrd0kME-9Gz0ha3Vt_igqFEiPAy5PaQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
Hello!
libgo is now able to automatically determine PtraceRegs. Attached
patch removes duplicate manual definition from system dependent
source.
Bootstrapped and regression tested on alphaev68-linux-gnu.
Uros.
[-- Attachment #2: g.diff.txt --]
[-- Type: text/plain, Size: 833 bytes --]
Index: go/syscall/syscall_linux_alpha.go
===================================================================
--- go/syscall/syscall_linux_alpha.go (revision 249592)
+++ go/syscall/syscall_linux_alpha.go (working copy)
@@ -8,38 +8,6 @@
import "unsafe"
-type PtraceRegs struct {
- R0 uint64
- R1 uint64
- R2 uint64
- R3 uint64
- R4 uint64
- R5 uint64
- R6 uint64
- R7 uint64
- R8 uint64
- R19 uint64
- R20 uint64
- R21 uint64
- R22 uint64
- R23 uint64
- R24 uint64
- R25 uint64
- R26 uint64
- R27 uint64
- R28 uint64
- Hae uint64
- Trap_a0 uint64
- Trap_a1 uint64
- Trap_a2 uint64
- Ps uint64
- Pc uint64
- Gp uint64
- R16 uint64
- R17 uint64
- R18 uint64
-}
-
func (r *PtraceRegs) PC() uint64 {
return r.Pc
}
next reply other threads:[~2017-06-26 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 7:24 Uros Bizjak [this message]
2017-06-26 17:59 ` 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=CAFULd4bkZ4v6YziJPgRxrd0kME-9Gz0ha3Vt_igqFEiPAy5PaQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--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).