From: Ian Lance Taylor <iant@golang.org>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: Re: [libgo] Remove Solaris 11.1+ zone_net_addr_t treatment
Date: Wed, 08 Apr 2015 14:17:00 -0000 [thread overview]
Message-ID: <CAKOQZ8y0N2MQjtXC5nHDk5wOWhn2Hryaip8nmUc176AGTyxO_A@mail.gmail.com> (raw)
In-Reply-To: <yddd23e679j.fsf@CeBiTec.Uni-Bielefeld.DE>
On Wed, Apr 8, 2015 at 7:10 AM, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
> Ian Lance Taylor <iant@golang.org> writes:
>
>> On Wed, Apr 8, 2015 at 6:48 AM, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
>>> Ian Lance Taylor <iant@golang.org> writes:
>>>
>>>> On Mon, Nov 3, 2014 at 8:59 AM, Rainer Orth
>>>> <ro@cebitec.uni-bielefeld.de> wrote:
>>>>>
>>>>> The recent godump changes broke Solaris 11.1+ bootstrap in libgo:
>>>>> before, gen-sysinfo.so had
>>>>>
>>>>> type _zone_net_addr_t struct { zna_family uint16; zna_plen uint16;
>>>>> zna_addru struct { znau_addr6 _in6_addr; }; }
>>>>>
>>>>> which was filtered out by mksysinfo.sh due to the use of _in6_addr.
>>>>>
>>>>> After the change, there's now
>>>>>
>>>>> type _zone_net_addr_t struct { zna_family uint16; zna_plen uint16;
>>>>> zna_addru struct { znau_addr6 [16]byte; Godump_0_align [0]uint32; }; }
>>>>>
>>>>> instead, not filtered, but added a second time by the _zone_net_addr_t
>>>>> code in mksysinfo.sh, which leads to redefinition warnings/errors.
>>>>>
>>>>> Simply removing the old _zone_net_addr_t fragment fixes this and
>>>>> restores bootstrap.
>>>>>
>>>>> Bootstrapped without regressions on i386-pc-solaris2.1[01], ok for
>>>>> mainline?
>>>>
>>>>
>>>> I just got back to this. Committed to mainline. Thanks.
>>>
>>> Sorry for the late reply, but between the time I submitted the patch and
>>> you committing it, something changed and the mksysinfo.sh fragment
>>> became necessary again. In fact, without it Solaris 11 bootstrap is
>>> broken.
>>
>> To avoid any confusion, can you send me the patch I should apply to mainline?
>
> Sure: here's what I have in my tree.
Committed.
Ian
prev parent reply other threads:[~2015-04-08 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 16:59 Rainer Orth
2015-02-06 16:18 ` Ian Lance Taylor
2015-04-08 13:49 ` Rainer Orth
2015-04-08 14:08 ` Ian Lance Taylor
2015-04-08 14:10 ` Rainer Orth
2015-04-08 14:17 ` 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=CAKOQZ8y0N2MQjtXC5nHDk5wOWhn2Hryaip8nmUc176AGTyxO_A@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).