From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Ian Lance Taylor <iant@golang.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Update to Go1.8rc1
Date: Tue, 17 Jan 2017 16:10:00 -0000 [thread overview]
Message-ID: <ed56e8d1-686b-8d8c-6c16-d80722bfeab3@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOyqgcXSYh2Yh9RtyuJp4JJPtrQESNZr5WaRXoVUk42koKtpWw@mail.gmail.com>
I think this is missing the update of the libgo version number.
- Lynn
On 01/13/2017 06:05 PM, Ian Lance Taylor wrote:
> I committed a patch to libgo to update the library to the first
> release candidate of the upcoming Go 1.8 release. This is a big
> update, mostly a straight copy of the code in the master Go library.
>
> I made the following changes to the Go frontend to correspond to
> changes in the runtime library:
>
> * Change map assignment to use mapassign and assign value directly.
> * Change string iteration to use decoderune, faster for ASCII strings.
> * Change makeslice to take int, and use makeslice64 for larger values.
> * Add new noverflow field to hmap struct used for maps.
>
> There are two known problems that I simply commented out of test code
> until they can be fixed:
>
> * Commented out test in go/types/sizes_test.go that doesn't compile.
> * Commented out reflect.TestStructOf test for padding after zero-sized field.
>
> As usual with these sorts of updates the patch is too large to send to
> the mailing list. I've appended the changes to the gccgo-specific
> parts of the code.
>
> Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. I would not
> be terribly surprised if this breaks Solaris. I'll try to check that
> out shortly.
>
> Ian
>
> gotools/ChangeLog:
>
> 2017-01-13 Ian Lance Taylor <iant@golang.org>
>
> Updates for Go 1.8rc1.
> * Makefile.am (go_cmd_go_files): Add bug.go.
> (s-zdefaultcc): Write defaultPkgConfig.
next prev parent reply other threads:[~2017-01-17 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 0:06 Ian Lance Taylor
2017-01-15 11:12 ` Andreas Schwab
2017-01-15 18:08 ` Rainer Orth
2017-01-16 1:05 ` Ian Lance Taylor
2017-01-16 1:21 ` Ian Lance Taylor
2017-01-16 15:22 ` Rainer Orth
2017-01-16 16:21 ` Rainer Orth
2017-01-18 3:56 ` Ian Lance Taylor
2017-01-19 15:53 ` Rainer Orth
2017-01-17 16:10 ` Lynn A. Boger [this message]
2017-01-17 16:12 ` Jakub Jelinek
2017-01-17 16:47 ` Lynn A. Boger
2017-01-23 18:15 ` 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=ed56e8d1-686b-8d8c-6c16-d80722bfeab3@linux.vnet.ibm.com \
--to=laboger@linux.vnet.ibm.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).