From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, gofrontend-dev@googlegroups.com
Subject: Re: Go patch committed: Update to current Go library
Date: Thu, 26 May 2011 11:11:00 -0000 [thread overview]
Message-ID: <ydd39k1oi7j.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <mcrwrhe8fpe.fsf@coign.corp.google.com> (Ian Lance Taylor's message of "Wed, 25 May 2011 17:31:57 -0700")
Ian Lance Taylor <iant@google.com> writes:
> Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>
>> * While I get
>>
>> // var ___iob [59+1]___FILE
>>
>> now, there's still
>>
>> var __lastbuf *_FILE
>>
>> left, with commented
>>
>> // type _FILE struct { _cnt int32; _ptr *uint8; _base *uint8; _flag uint8; _file
>> uint8; __orientation INVALID-bit-field; __ionolock INVALID-bit-field; __seekabl
>> e INVALID-bit-field; __extendedfd INVALID-bit-field; __xf_nocheck INVALID-bit-fi
>> eld; __filler INVALID-bit-field; }
>>
>> as before.
>>
>> * The amd64 sysinfo.go contains several undefined types:
>>
>> sysinfo.go:2886:53: error: use of undefined type '_fpchip_state'
>> sysinfo.go:2886:40: error: struct field type is incomplete
>> sysinfo.go:2886:53: error: use of undefined type '_fpchip_state'
>> sysinfo.go:2887:47: error: struct field type is incomplete
>> sysinfo.go:2892:32: error: use of undefined type '_fxsave_state'
>> sysinfo.go:2892:24: error: struct field type is incomplete
>
> This patch should fix these problems. Bootstrapped and ran Go testsuite
> on x86_64-unknown-linux-gnu. Committed to mainline.
Yes, I could just successfully bootstrap mainline on i386-pc-solaris2.10
without any workarounds.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-05-26 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 9:44 Ian Lance Taylor
2011-05-20 14:18 ` Rainer Orth
2011-05-20 14:37 ` Jakub Jelinek
2011-05-20 19:31 ` Ian Lance Taylor
2011-05-20 18:09 ` Rainer Orth
2011-05-24 22:41 ` Ian Lance Taylor
2011-05-20 18:26 ` Rainer Orth
2011-05-24 23:33 ` Ian Lance Taylor
2011-05-25 0:24 ` Ian Lance Taylor
2011-05-24 21:33 ` Ian Lance Taylor
2011-05-25 19:11 ` Rainer Orth
2011-05-26 6:36 ` Ian Lance Taylor
2011-05-26 11:11 ` Rainer Orth [this message]
2011-05-26 9:04 ` Ian Lance Taylor
2011-05-24 22:01 ` 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=ydd39k1oi7j.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@google.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).