{"push_id":1731789870,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"01b24b6e14719f78b6a081a08ac94c80cf3eada3","before":"ab475e65fc07a91fb0194229dbfc231b9915eefb","commits":[{"sha":"03118c210b2bf41242268736e16e9088293277b9","author":{"name":"ian","email":"668fd45181c31193793d12a7f2ecb1f2376600d1@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"Big merge of changes to gofrontend repo that were postponed due to the\nGCC release freeze.\n\n\t* go-backend.c: Include \"go-c.h\".\n\t* go-gcc.cc (Gcc_backend::write_export_data): New method.\n\n\t* go-gcc.cc (Gcc_backend::Gcc_backend): Declare\n\t__builtin_prefetch.\n\t* Make-lang.in (GO_OBJS): Add go/wb.o.\n\ncommit 884c9f2cafb3fc1decaca70f1817ae269e4c6889\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Mon Jan 23 15:07:07 2017 -0500\n\n    compiler: insert additional conversion for type desc ptr expr\n    \n    Change the method Type::type_descriptor_pointer to apply an additional\n    type conversion to its result Bexpression, to avoid type clashes in\n    the back end. The backend expression for a given type descriptor var\n    is given a type of \"_type\", however the virtual calls that create the\n    variable use types derived from _type, hence the need to force a\n    conversion.\n    \n    Reviewed-on: https://go-review.googlesource.com/35506\n\n\ncommit 5f0647c71e3b29eddcd0eecc44e7ba44ae7fc8dd\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Mon Jan 23 15:22:26 2017 -0500\n\n    compiler: insure tree integrity in Call_expression::set_result\n    \n    Depending on the back end, it can be problematic to reuse Bexpressions\n    (passing the same Bexpression to more than one Backend call to create\n    additional Bexpressions or Bstatements). The Call_expression::set_result\n    method was reusing its Bexpression input in more than one tree\n    context; the fix is to pass in an Expression instead and generate\n    multiple Bexpression references to it within the method.\n    \n    Reviewed-on: https://go-review.googlesource.com/35505\n\n\ncommit 7a8e49870885af898c3c790275e513d1764a2828\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Tue Jan 24 21:19:06 2017 -0800\n\n    runtime: copy more of the scheduler from the Go 1.8 runtime\n    \n    Copies mstart, newm, m0, g0, and friends.\n    \n    Reviewed-on: https://go-review.googlesource.com/35645\n\n\ncommit 3546e2f002d0277d805ec59c5403bc1d4eda4ed9\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Jan 26 19:47:37 2017 -0800\n\n    runtime: remove a few C functions that are no longer used\n    \n    Reviewed-on: https://go-review.googlesource.com/35849\n\n\ncommit a71b835254f6d3164a0e6beaf54f2b175d1a6a92\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Jan 26 16:51:16 2017 -0800\n\n    runtime: copy over more of the Go 1.8 scheduler\n    \n    In particular __go_go (aka newproc) and goexit[01].\n    \n    Reviewed-on: https://go-review.googlesource.com/35847\n\n\ncommit c3ffff725adbe54d8283c373b6aa7dc95d6fc27f\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Jan 27 16:58:20 2017 -0800\n\n    runtime: copy syscall handling from Go 1.8 runtime\n    \n    Entering a syscall still has to start in C, to save the registers.\n    Fix entersyscallblock to save them more reliably.\n    \n    This copies over the tracing code for syscalls, which we previously\n    weren't doing, and lets us turn on runtime/trace/check.\n    \n    Reviewed-on: https://go-review.googlesource.com/35912\n\n\ncommit d5b921de4a28b04000fc4c8dac7f529a4a624dfc\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Jan 27 18:34:11 2017 -0800\n\n    runtime: copy SIGPROF handling from Go 1.8 runtime\n    \n    Also copy over Breakpoint.\n    \n    Fix Func.Name and Func.Entry to not crash on a nil Func.\n    \n    Reviewed-on: https://go-review.googlesource.com/35913\n\n\ncommit cc60235e55aef14b15c3d2114030245beb3adfef\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Mon Feb 6 11:12:12 2017 -0500\n\n    compiler: convert go_write_export_data to Backend method.\n    \n    Convert the helper function 'go_write_export_data' into a Backend\n    class method, to allow for an implementation of this function that\n    needs to access backend state.\n    \n    Reviewed-on: https://go-review.googlesource.com/36357\n\n\ncommit e387439bfd24d5e142874b8e68e7039f74c744d7\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Wed Feb 8 11:13:46 2017 -0500\n\n    compiler: insert backend conversion in temporary statement init\n    \n    Insert an additional type conversion in Temporary_statement::do_get_backend\n    when assigning a Bexpression initializer to the temporary variable, to\n    avoid potential clashes in the back end. This can come up when assigning\n    something of concrete pointer-to-function type to a variable of generic\n    pointer-to-function type.\n    \n    Reviewed-on: https://go-review.googlesource.com/36591\n\n\ncommit c5acf0ce09e61ff623847a35a99da465b8571609\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 1 17:57:53 2017 +0100\n\n    libgo: build tags for aix\n    \n    Build tags for the libgo source files required to build\n    libgo on AIX.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37633\n\n\ncommit 67ed19616898ea18a101ec9325b82d028cd395d9\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 2 15:41:31 2017 +0100\n\n    libgo: handle AIX tag in match.sh and gotest\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37638\n\n\ncommit 83ea2d694c10b2dd83fc8620c43da13d20db754e\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 1 17:48:16 2017 +0100\n\n    libgo: add AIX support in configure and Makefile\n    \n    - support for GOOS=aix\n    - CFLAGS/GOCFLAGS/LDFLAGS for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37632\n\n\ncommit 35d577fe22ffa16a3ccaadf5dae9f6f425c8ec8c\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Mon Mar 6 15:00:15 2017 +0100\n\n    runtime: adapt memory management to AIX mmap\n    \n    On AIX:\n    * mmap does not allow to map an already mapped range,\n    * mmap range start at 0x30000000 for 32 bits processes,\n    * mmap range start at 0x70000000_00000000 for 64 bits processes\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37845\n\n\ncommit 4e49e56a5fd4072b4ca7fcefe4158d6885d9ee62\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Mon Mar 6 13:42:26 2017 +0100\n\n    runtime: add getproccount implementation for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37844\n\n\ncommit ff626470294237ac664127894826614edc46a3d0\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Mon Mar 6 17:31:21 2017 +0100\n\n    runtime: handle ERESTART errno with AIX's wait4\n    \n    On AIX, wait4 may return with errno set to ERESTART, which causes unexepected\n    behavior (for instance, go build may exit with the message \"wait: restart\n    system call\" after running a command, even if it was successfull).\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37846\n\n\ncommit 37daabbfc83d533b826ef9ab10e2dee7406e7198\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Mon Mar 6 11:02:58 2017 +0100\n\n    runtime: support for AIX's procfs tree\n    \n    On AIX, the process executable file is available under /proc/<pid>/object/a.out\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37842\n\n\ncommit a0275c039d56acf4bf48151978c1a4ec5758cc2c\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Mar 8 07:00:05 2017 -0800\n\n    libgo/Makefile.am: don't use nonportable \\n or \\t in sed expression\n    \n    The resulting zstdpktlist.go is less pretty, but it works.\n    \n    Reviewed-on: https://go-review.googlesource.com/37940\n\n\ncommit 29b190f76105aafa2b50b48249afdafecc97a4be\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 9 16:02:34 2017 +0100\n\n    runtime: netpoll and semaphores for AIX\n    \n    semaphore implementation based on Solaris implementation in\n    libgo/go/runtime/os_solaris.go\n    \n    netpoll is just a stub to avoid build failure on AIX.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37966\n\n\ncommit 55ca6d3f3cddf0ff9ccb074b2694da9fc54de7ec\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 9 15:38:30 2017 +0100\n\n    libmain: ensure initfn is called when loading a go library\n    \n    AIX does not support .init_array.\n    The alterative is to export the __go_init function and tell the linker\n    it is an init function with the -Wl,-binitfini:__go_init option.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37965\n\n\ncommit 349a30d17d880ac8bc1a35e1a2ffee6d6e870ae9\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Mar 10 11:15:08 2017 +0100\n\n    libgo: use an import list for missing symbols\n    \n    libgo depends on symbols provided by Go programs at runtime. On AIX,\n    this requires either to build libgo with -Wl,-berok linker option and\n    the programs with -Wl,-brtl, or to provide a list of imported symbols\n    when building libgo. The second options seems preferable, to avoid\n    requiring an additional option for every Go program.\n    \n    There are also some symbols that are specific to GNU ld and do not\n    exist when linking with AIX ld (__data_start, __edata, __etext and\n    __bss_start).\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37969\n\n\ncommit 91db0ea1ff068ca1d97b9c99612100ea5b96ddb2\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 8 15:34:45 2017 +0100\n\n    crypto/x509: add certificate files locations for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/37952\n\n\ncommit 92e521c854e91709b949548c47e267377850f26a\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Mar 10 14:10:11 2017 -0800\n\n    compiler: fix check for pointer in Temporary_reference_expression\n    \n    The check for an unrepresentable pointer in\n    Temporary_reference_expression::do_get_backend was incorrectly\n    translated from C to Go in https://golang.org/cl/14346043.  Fix the\n    check to use points_to rather than has_pointer and deref.  This should\n    not make any difference in practice as either way the condition will\n    only be true for a pointer to void, but points_to is correct and more\n    efficient.\n    \n    Reviewed-on: https://go-review.googlesource.com/38009\n\n\ncommit 9a0b676e59e7171a630c48fdc3d4de6712bad0ca\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 16 16:51:53 2017 +0100\n\n    libgo: add missing _arpcom struct to *sysinfo.go\n    \n    This struct is filtered due to having a field of type _in6_addr,\n    but other types exported to *sysinfo.go are depending on it.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38251\n\n\ncommit 61262a757bdd3d9a595ab6a90f68c0c4ebed7bc1\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 16 18:27:46 2017 +0100\n\n    syscall: raw_ptrace stub for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38253\n\n\ncommit 8029632b50880fd9b5e39299c738b38e3386595f\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 15 16:58:37 2017 +0100\n\n    libgo: adapt runtime.inc to AIX\n    \n    * Two AIX types are wrongfully exported to runtime.inc as their names\n      make them look like a Go type.\n    * The sigset go type conflicts with a system sigset type.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38192\n\n\ncommit 25f3a90d14bc268479369ecc0eada72791612f86\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 15 16:58:37 2017 +0100\n\n    libgo: update Makefile.in, accidentally omitted from last change\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38310\n\n\ncommit d52b4895616b66f93b460366527e74336829aaa5\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 16 18:39:26 2017 +0100\n\n    syscall: TIOCSCTTY does not exist on AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38254\n\n\ncommit ff1ec3847a4472008e5d53a98b6694b1e54ca322\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 16 18:07:34 2017 +0100\n\n    syscall: syscall does not exist on AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38252\n\n\ncommit c1ee60dabf0b243a0b0286215481a5d326c34596\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Mar 17 17:18:18 2017 +0100\n\n    net: EAI_OVERFLOW does not exist on AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38266\n\n\ncommit ad4ad29aed9f70b14b39b488bfeb9ee745382ec4\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Mar 17 17:23:56 2017 +0100\n\n    net: sockopt/sockoptip stubs for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38267\n\n\ncommit 5d7db2d7542fe7082f426d42f8c2ce14aad6df55\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Mar 17 16:35:05 2017 +0100\n\n    os/user: add listgroups stub for AIX\n    \n    This is required to build os/user.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38263\n\n\ncommit 4e57a7973e9fa4cb5ab977c6d792e62a8f7c5795\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 22 11:11:30 2017 +0100\n\n    os: fix readdirnames for AIX\n    \n    Largefile implementation should be used on AIX.\n    \n    readdir64_r function returns 9 and sets result to NULL when\n    reaching end of directory, so this return code should not\n    always be considered as an error.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38359\n\n\ncommit b34036967d1ec57b25e3debe077439b4210a1d4a\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Mar 17 17:39:31 2017 +0100\n\n    libgo: adapt sigtab.go to AIX\n    \n    On AIX, _NSIG is not directly defined to its integer value in\n    gen-sysinfo.go.\n    The real value is _SIGMAX32+1 or _SIGMAX64+1, depending if we are\n    building a 32bit ligbo or a 64bit libgo, so we need to read one of\n    those constants to set nsig value in mksigtab.sh\n    \n    This change also ensures that all signal numbers from 0 to nsig-1\n    are referenced in sigtable.\n    \n    Reviewed-on: https://go-review.googlesource.com/38268\n\n\ncommit 20991c32671a183ec859b4f285df37fdd4634247\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 23 17:28:09 2017 +0100\n\n    syscall: missing import in socket_bsd.go\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38369\n\n\ncommit c34754bd9adf5496c4c26257eaa50793553c11e8\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 22 17:57:01 2017 +0100\n\n    sycall: WCOREDUMP macro is not defined on AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38363\n\n\ncommit 4f38813482227b12ea0ac6ac1b981ff9ef9853ef\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 23 17:44:43 2017 +0100\n\n    libgo: additional build tags for AIX\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38510\n\n\ncommit d117ede6ff5a7083e9c40eba28a0f94f3535d773\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 23 17:48:46 2017 +0100\n\n    go/build: add AIX to \"go build\" command known OS\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38511\n\n\ncommit 7b0ddaa6a6a71f9eb1c374122d29775b13c2cac5\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Mar 23 09:57:01 2017 -0700\n\n    compiler: don't crash if imported package imports this one\n    \n    When building a test it's OK if test code imports a package that\n    imports this one. The go tool is supposed to catch cases where this\n    creates an impossible initialization order. The compiler already has\n    code to permit this in Gogo::add_import_init_fn. This CL avoids a\n    compiler crash on a similar case when writing out the export data.\n    \n    I have no test case for this. Basically it pushes a compiler crash\n    into an error reported elsewhere.\n    \n    Problem was reported by Tony Reix.\n    \n    Reviewed-on: https://go-review.googlesource.com/38462\n\n\ncommit 925636975d075e3e3353823b09db3f933f23cb03\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Mar 29 14:14:18 2017 -0700\n\n    runtime: copy finalizer support from Go 1.8 runtime\n    \n    Reviewed-on: https://go-review.googlesource.com/38794\n\n\ncommit 1ccb22b96cb3b1011db0e427877d9ddecb577fa9\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Mar 30 15:21:06 2017 +0200\n\n    runtime: initcontext and setcontext stubs for AIX\n    \n    Further investigations are required to understand the clobbering\n    issue and implement a proper fix. Until then, those stubs are\n    required to allow the build to complete.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38930\n\n\ncommit 27db481f369b54256063c72b911d22390c59199c\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 29 18:07:25 2017 +0200\n\n    os: fix Readlink failure on AIX\n    \n    AIX readlink routine returns an error if the link is longer\n    than the buffer, instead of truncating the link.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38700\n\n\ncommit c93babbf48eddd0bc34d4179ffb302dc60087299\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 29 17:26:35 2017 +0200\n\n    compiler: implement support for reading AIX big archives\n    \n    This is required to read go export from a Go library.\n    \n    Code courtesy of Damien Bergamini from Atos Infogérance.\n    \n    Issue golang/go#19200\n    Reviewed-on: https://go-review.googlesource.com/38698\n\n\ncommit 930dd53482bdee3a9074850d168d0b9d7819c135\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 6 18:50:11 2017 -0700\n\n    compiler: fix whether conversions are static initializers\n    \n    The compiler was incorrectly treating type conversions from string to\n    int or vice-versa as static initializers.  That doesn't work, as those\n    conversions are implemented via a function call.\n    \n    This case may never actually arise but it seems like the right thing to do.\n    \n    Reviewed-on: https://go-review.googlesource.com/39872\n\n\ncommit f02691e4195728dbf06f4dde0853c6bccc922183\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 6 17:24:08 2017 -0700\n\n    compiler, runtime: don't let slices point past end of memory block\n    \n    When Go code uses a slice expression like [:len(str)] or [:cap(slice)],\n    it's natural for the resulting pointer to point just past the end of\n    the memory block.  If the next memory block is not live, we now have a\n    live pointer to a dead block, which will unnecessarily keep the block\n    alive.  That wastes space, and with the new Go 1.8 GC (not yet\n    committed) will trigger an error when using GODEBUG=gccheckmark=1.\n    \n    This changes the implementation of slice expressions to not move the\n    pointer if the resulting string length or slice capacity is 0.  When\n    the length/capacity is zero, the pointer is never used anyhow.\n    \n    Reviewed-on: https://go-review.googlesource.com/39870\n\n\ncommit 17527c35b027e1afcc318faf5563909e1e9d44a6\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 6 15:30:11 2017 -0700\n\n    compiler: emit write barriers\n    \n    The Go 1.8 concurrent GC requires optional write barriers for all\n    assignments that may change pointer values in the heap or in a global\n    variable.  For details see https://blog.golang.org/go15gc.\n    \n    This changes the gofrontend code to emit write barriers as needed.\n    This is in preparation for future changes.  At the moment the write\n    barriers will do nothing.  They test runtime.writeBarrier.enabled,\n    which will never be non-zero.  They call simple functions which just\n    do a move without doing any of the other operations required by the\n    write barrier.\n    \n    Reviewed-on: https://go-review.googlesource.com/39852\n\n\ncommit c0b00f072bf34b2c288e1271ec8118b88c4f6f6f\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Tue Apr 11 17:47:29 2017 +0200\n\n    libgo: allow building gox files from PIC objects\n    \n    libtool builds non-PIC objects in the same directory as .lo files\n    and PIC objects in a .libs subdirectory.\n    BUILDGOX rule uses the non-PIC objects to build the gox files,\n    but on AIX only the PIC objects are built.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/40355\n\n\ncommit ea0f3da174c5503a209043f14ddda34871cfec52\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 6 19:06:14 2017 -0700\n\n    compiler: add code to generate a ptrmask for a type\n    \n    The Go 1.8 garbage collector uses a ptrmask for all types below a\n    certain size.  A ptrmask is simply a bit vector with a single bit for\n    each pointer-sized word in the value.  The bit is 1 if the type has a\n    pointer in that position, 0 if it does not.\n    \n    This change adds code to the compiler to generate a ptrmask.  The code\n    is not used by anything yet, it is just compiled.  It will be used\n    when we switch over to the Go 1.8 garbage collector.\n    \n    The new Array_type::int_length method, and the new memory_size\n    methods, will also be used by other patches coming later.\n    \n    Reviewed-on: https://go-review.googlesource.com/39873\n\n\ncommit 3029e1df3be3614d196a03c15e50e68ff850aa4c\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 7 10:31:39 2017 -0700\n\n    compiler: add code to generate a gcprog for a type\n    \n    The Go 1.8 garbage collector uses a gcprog for all types above a\n    certain size.  A gcprog describes where the pointers are in the type,\n    using a simple bytecode machine that supports repeating bits.  The\n    effect is to permit using much less space to describe arrays.  The\n    format is described in runtime/mbitmap.go in the docs for runGCProg.\n    This is not yet added to the gofrontend, but can be seen in the gc sources.\n    \n    This change adds code to the compiler to generate a gcprog.  The code\n    is not used by anything yet, it is just compiled.  It will be used\n    when we switch over to the Go 1.8 garbage collector.\n    \n    Reviewed-on: https://go-review.googlesource.com/39923\n\n\ncommit 8b01ef1e9176d20f4c9e667972fe031069a4d057\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 13 07:00:35 2017 -0700\n\n    compiler: add ptrdata computations and expressions\n    \n    For the upcoming Go 1.8 GC we need to compute the \"ptrdata\" of a type:\n    the number of bytes in the type that can contain pointers.  For types\n    that do not contain pointers this number is zero.  For many types it\n    is a number larger than zero but smaller than the total size of the\n    type.  The Go 1.8 GC uses this number to make loops looking for\n    pointers run faster by not scanning the suffix of a value that can not\n    contain a pointer.\n    \n    Unfortunately there are two subtly different definitions of ptrdata,\n    and we need both.  The first is the simple one: the prefix that can\n    contain pointers.  The second is the number of bytes described by the\n    gcprog for the type.  Recall that we describe the exact position of\n    pointers in a type using either a ptrmask or a gcprog.  The ptrmask is\n    simpler, the gcprog uses less space.  We use the gcprog for large\n    types, currently defined as types that are more than 2048 bytes.  When\n    the Go 1.8 runtime expands a gcprog, it verifies that the gcprog\n    describes exactly the same number of bytes as the ptrdata field in the\n    type descriptor.  If the last pointer-containing portion of a type is\n    an array, and if the elements of the array have a ptrdata that is less\n    than the size of the element type, then the simple definition of the\n    ptrdata will not include the final non-pointer-containing bytes of the\n    last element of the array.  However, the gcprog will define the array\n    using a repeat count, and will therefore include the full size of the\n    last element of the array.  So for a type that needs a gcprog, the\n    ptrdata field in the type descriptor must be the size of the data\n    described by the gcprog, and that is not necessarily the same as the\n    simple ptrdata.\n    \n    It might seem that we can always use the gcprog version of the ptrdata\n    calculation, since that is what will appear in a type descriptor, but\n    it turns out that for global variables we always use a ptrmask, not a\n    gcprog, even if the global variable is large.  This is because gcprogs\n    are handled by expanding them into a ptrmask at runtime, and for a\n    global variable there is no natural place to put the ptrmask.  Simpler\n    to always use the ptrmask.  That means that we need to describe the\n    size of the ptrmask, and that means that we need an expression for the\n    simple form of the ptrdata.\n    \n    This CL implements the ptrdata calculation.  This code is not actually\n    used yet.  It will be used later when the Go 1.8 GC is committed.\n    \n    Reviewed-on: https://go-review.googlesource.com/40573\n\n\ncommit 7a37331303b572412179a08141f1dd35339d40c8\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 06:55:48 2017 -0700\n\n    compiler: zero length arrays never contain pointers\n    \n    Reviewed-on: https://go-review.googlesource.com/40696\n\n\ncommit c242f0508a64d3d74a28d498cbaeda785ff76258\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 07:26:54 2017 -0700\n\n    bytes: disable allocations test on gccgo\n    \n    It turns out that testing.AllocsPerRun has not been producing correct\n    results with the current gccgo memory allocator.  When we update to\n    the Go 1.8 memory allocator, testing.AllocsPerRun will work again, and\n    this test will fail due to lack of escape analysis.\n    \n    Reviewed-on: https://go-review.googlesource.com/40700\n\n\ncommit 0dc369f1d63376a36bfb0999a1b0377fd444bfab\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Tue Apr 11 16:22:38 2017 +0200\n\n    os: alternative way to find executable path, using Args[0]\n    \n    AIX does not provide a proper way to find the original\n    executable path from procfs, which contains just an\n    hardlink.\n    Executable path can be found using Args[0], Getcwd and\n    $PATH.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/40353\n\n\ncommit f9bad1342569b338e3b2ea9f12ffc6d3d3fa3028\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 08:01:19 2017 -0700\n\n    compiler: don't write struct with multiple sink fields to C header file\n    \n    When writing a struct to the C header file used by the C runtime code,\n    a single sink field is fine: it will be called \"_\", which is valid C.\n    There are structs with single sink fields that we want to write out,\n    such as finblock.  As it happens, though, the Go 1.8 runtime has a\n    struct with two sink fields, gcControllerState, which will produce a C\n    definition with two fields named \"_\", which will fail.  Since we don't\n    need to know that struct in C, rather than fix the general case, just\n    punt if the struct has multiple sink fields.\n    \n    After the conversion to the Go 1.8 GC, we may be able to get rid of\n    the C header file anyhow.  I'm not sure yet.\n    \n    Reviewed-on: https://go-review.googlesource.com/40701\n\n\ncommit cfc28901a572aeb15b2f10a38f79eec04c64dfb2\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 10:07:23 2017 -0700\n\n    runtime: disable allocations test on gccgo\n    \n    It turns out that testing.AllocsPerRun has not been producing correct\n    results with the current gccgo memory allocator.  When we update to\n    the Go 1.8 memory allocator, testing.AllocsPerRun will work again, and\n    these tests will fail due to lack of escape analysis.\n    \n    Reviewed-on: https://go-review.googlesource.com/40703\n\n\ncommit 36fedd76edaa48b9ec09709a70d9e4abaddf0caf\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 10:47:06 2017 -0700\n\n    runtime: remove unused size argument from hash/equal fns\n    \n    The size argument was removed from hash and equal functions in CL\n    34983.  Somehow I missed removing them from three of the predefined\n    functions.\n    \n    Reviewed-on: https://go-review.googlesource.com/40770\n\n\ncommit 90f6accb48d2e78cad8955b9292933f6ce3fe4c8\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 13:23:05 2017 -0700\n\n    runtime: remove unused stack.go\n    \n    We're never going to use stack.go for gccgo.  Although a build tag\n    keeps it from being built, even having it around can be confusing.\n    Remove it.\n    \n    Reviewed-on: https://go-review.googlesource.com/40774\n\n\ncommit befa71603fc66a214e01ac219f2bba36e19f136f\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 13:18:34 2017 -0700\n\n    runtime: build fastlog\n    \n    Take out the build tags which were preventing fastlog2 from being\n    built.  It's used by the upcoming Go 1.8 GC.\n    \n    Reviewed-on: https://go-review.googlesource.com/40773\n\n\ncommit b7e19e9be4ab4c3cd8f4c9506d79a8cd56bace40\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Fri Apr 14 10:04:23 2017 -0700\n\n    runtime: add tests from Go 1.8\n    \n    Some runtime package tests never made it into the gofrontend repo for\n    some reason.  Add them now.\n    Reviewed-on: https://go-review.googlesource.com/40869\n\n\ncommit 1feef185aebd71bc2a09b9a04287461806096610\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Mon Apr 17 16:26:11 2017 -0700\n\n    runtime: change mcall to take a Go function value\n    \n    For future work in bringing in the Go 1.8 GC, change the mcall\n    function to take a Go function value, which means that mcall can take\n    a closure rather than just a straight C function pointer.\n    \n    As part of this change move kickoff from C to Go, which we want to do\n    anyhow so that we run the write barriers that it generates.\n    \n    Reviewed-on: https://go-review.googlesource.com/40935\n\n\ncommit c3db34f4efc2d610f74a01dd2ad7775f48889b29\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Tue Apr 11 16:11:26 2017 +0200\n\n    runtime: netpoll implementation for AIX\n    \n    Code courtesy of Damien Bergamini from Atos Infogérance.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/40352\n\n\ncommit f5634dff40e53ad9ce61afd67fd07334e3af9d1f\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Tue Apr 18 22:06:07 2017 -0700\n\n    runtime: move mstart from Go to C\n    \n    The assignments done in mstart must be done without write barriers, as\n    mstart is running without an m or p.  In the gc toolchain the\n    equivalent code to intialize g and g->m is written in assembler;\n    on GNU/Linux, it's in the clone function.\n    \n    Reviewed-on: https://go-review.googlesource.com/40989\n\n\ncommit 671d7c74592f4b6fe3665af279482ba0ea47ca2d\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Tue Apr 18 17:47:28 2017 -0700\n\n    compiler: varargs slices do not escape in runtime\n    \n    Also, don't try to allocate an empty slice on the stack, as it will\n    confuse the GCC backend.\n    \n    Also add a few trivial style, code formatting, and debug output fixes.\n    \n    Updates golang/go#17431\n    \n    Reviewed-on: https://go-review.googlesource.com/40983\n\n\ncommit 94699d25f31353bf03419eda56b15993a39f3275\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Tue Apr 18 17:30:09 2017 -0700\n\n    compiler: add Ptrmask_symbol_expression\n    \n    Add an expression to evaluate to the ptrmask for a type.  This will be\n    used for global variables, which always use a ptrmask no matter how\n    large they are.\n    \n    Reviewed-on: https://go-review.googlesource.com/40981\n\n\ncommit bfff1654eac5b9288fa6c431e66cba8c9da6a660\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Mon Apr 17 10:51:16 2017 -0700\n\n    runtime: change g's in systemstack\n    \n    The systemstack function in the gc toolchain changes to a different g.\n    This is often used to get more stack space; the gofrontend uses a\n    different stack growth mechanism that does not require changing g's,\n    so we've been running with a version of systemstack that keeps the\n    same g.  However, the garbage collector has various tests to verify\n    that it is running on g0 rather than on a normal g.  For simplicity,\n    change the gofrontend version of systemstack to change to a different\n    g just as the gc toolchain does.\n    \n    This permits us to uncomment some sanity checks in notetsleep.\n    Doing that requires us to fix up a couple of places where C code calls\n    {start,stop}TheWorldWithSema while not on g0.\n    \n    Note that this does slow down some code in the runtime package unnecessarily.\n    It may be useful to find some places where the runtime calls\n    systemstack only to get more stack space and change it to use some\n    other function.  That other function would act like systemstack in the\n    gc toolchain but simply call the argument in the gofrontend.\n    \n    Reviewed-on: https://go-review.googlesource.com/40973\n\n\ncommit b2ccc7601ce71a7c5732154cf9b2eeea64681469\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 10:36:12 2017 -0700\n\n    compiler, runtime: include ptrmask in GC roots\n    \n    Change the list of registered GC roots to include a ptrmask,\n    and change the data structures to be easily used from Go code.\n    The new ptrmask will be used by the Go 1.8 GC to only scan pointers.\n    Tweak the current GC to use the new structures, but ignore the new\n    ptrmask information for now.\n    \n    The new GC root data includes the size of the variable.  The size is\n    not currently used, but will be used later by the cgo checking code.\n    \n    Reviewed-on: https://go-review.googlesource.com/41075\n\n\ncommit 9e065149970bc180e4ca83bb99c74d9c4f43b47b\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 12:23:16 2017 -0700\n\n    compiler, runtime: don't pass size to __go_new\n    \n    There is no reason to pass the size to __go_new, as the type\n    descriptor includes the size anyhow.  This makes the function\n    correspond to the Go 1.8 function runtime.newobject, which is what we\n    will use when we update to the Go 1.8 memory allocator.\n    \n    Reviewed-on: https://go-review.googlesource.com/41080\n\n\ncommit c321de7b738c4a3387c1842919c9305acfa04c57\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 13:13:56 2017 -0700\n\n    compiler, runtime, reflect: make type descriptors more like Go 1.8\n    \n    Change the type descriptor structure to be more like the one in the Go\n    1.8 runtime.  Specifically we add the ptrdata field, rename the gc\n    field to gcdata and change the type to *byte, and rearrange a few of\n    the fields.  The structure is still not identical to the Go 1.8\n    structure--we don't use any of the tricks to reduce overall executable\n    size--but it is more similar.\n    \n    For now we don't use the new ptrdata field, and the gcdata field is\n    still the old format rather than the new Go 1.8 ptrmask/gcprog format.\n    \n    Reviewed-on: https://go-review.googlesource.com/41081\n\n\ncommit 7b70c52cddeebea9ebeac003f8c6aad59497e5f0\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 14:54:29 2017 -0700\n\n    reflect: make sure to clear unusable hash/equal function\n    \n    Otherwise we wind up copying the one from the prototype, which is wrong.\n    \n    Also rewrite the hash/equal functions to look like the ones in Go 1.8,\n    mainly a matter of changing names and using arrayAt.\n    \n    Reviewed-on: https://go-review.googlesource.com/41133\n\n\ncommit 84d26f467f7de8bdbb0d230458135fe1b6b2a99d\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 14:59:13 2017 -0700\n\n    runtime: remove duplicate declarations of SetFinalizer/KeepAlive\n    \n    These should have been removed in CL 38794.  It's a bug that the\n    compiler even permits these duplicate declarations.\n    \n    Reviewed-on: https://go-review.googlesource.com/41134\n\n\ncommit f85ff7e64c24031f6d0bd7c9c426b6176cb95160\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 15:56:32 2017 -0700\n\n    runtime: don't crash if panicstring called with no m\n    \n    It's possible for runtime_panicstring to be called with no m if a\n    signal handler, or scheduler innards, do something wrong.  If that\n    happens carry on with the panic rather than crashing.\n    \n    Reviewed-on: https://go-review.googlesource.com/41137\n\n\ncommit 5b362b04f642afb8b20715930416fc3b7d91bb12\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Fri Mar 31 14:35:48 2017 -0400\n\n    compiler: fix for expr sharing introduced by Order_eval::statement.\n    \n    When processing an expression statement with a top-level call\n    that returns multiple results, Order_eval::statement can wind up\n    creating a tree that has multiple references to the same call,\n    which results in a confusing AST dump. Change the implementation\n    to avoid introducing this unwanted sharing.\n    \n    Reviewed-on: https://go-review.googlesource.com/39210\n\n\ncommit b05b4260a68695bf9c9cc29e14ae86ca2699458a\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 16:00:28 2017 -0700\n\n    runtime: restore correct m in gtraceback\n    \n    If gtraceback is used to get a stack trace of a g running in the same m,\n    as can happen if we collect a stack trace from a g0, then restore the\n    old m value, don't clear it.\n    \n    Reviewed-on: https://go-review.googlesource.com/41138\n\n\ncommit ca8bbf4dfac19b3f4f7ce21a688b96a418c75031\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 16:03:24 2017 -0700\n\n    runtime: set startpc field when starting a new goroutine\n    \n    This puts the right value in a trace--previously it was always zero.\n    \n    Reviewed-on: https://go-review.googlesource.com/41139\n\n\ncommit ca8bbf4dfac19b3f4f7ce21a688b96a418c75031\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 16:03:24 2017 -0700\n\n    runtime: set startpc field when starting a new goroutine\n    \n    This puts the right value in a trace--previously it was always zero.\n    \n    Reviewed-on: https://go-review.googlesource.com/41139\n\n\ncommit 887690dce42d7bf8f711f8ea082e4928fb70f2a5\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 17:06:11 2017 -0700\n\n    runtime: add prefetch functions\n    \n    The Go 1.8 GC uses prefetch functions.  Add versions for gccgo that\n    call __builtin_prefetch.  Uncomment the test for them in testAtomic64.\n    Don't force the check function to return early, as now taking the\n    address of a local variable in the runtime package does not force it\n    onto the heap.\n    \n    Reviewed-on: https://go-review.googlesource.com/41144\n\n\ncommit 4269db69f9184e5a45c54aaee7352425a1f88bff\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 17:55:21 2017 -0700\n\n    runtime: split up ticks to get correct alignment\n    \n    On 32-bit x86 a uint64 variable by itself is aligned to an 8-byte boundary.\n    A uint64 field in a struct is aligned to a 4-byte boundary.\n    The runtime.ticks variable has a uint64 field that must be aligned\n    to an 8-byte boundary.  Rather than rely on luck, split up the struct\n    into separate vars so that the required alignment happens reliably.\n    \n    It would be much nicer if issue golang/go#19057 were fixed somehow,\n    but that is for another day.\n    \n    Reviewed-on: https://go-review.googlesource.com/41143\n\n\ncommit 66926cabdbdbf3431b4f172f7756e195c1c6c513\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Apr 20 17:15:38 2017 +0200\n\n    libgo: fix bad value for O_CLOEXEC on AIX 7.1\n    \n    On AIX 7.1, O_CLOEXEC is defined as 0x0000001000000000, which\n    creates an integer constant overflow error when building libgo.\n    \n    This affects only 7.1, O_CLOEXEC is not defined on 6.1 (and\n    defaults to O in sysinfo.go) and is defined as 0x00800000 on\n    AIX 7.2.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/41214\n\n\ncommit af288ff10aeafc47651f5def327ed56425d5be19\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 20 17:15:02 2017 -0700\n\n    runtime: preserve stack context in tracebackothers\n    \n    The tracebackothers function works by saving the current stack context\n    in the goroutine's context field and then calling gogo to switch to a\n    new goroutine.  The new goroutine will collect its own stack trace and\n    then call gogo to switch back to the original goroutine.  This works\n    fine, but if the original goroutine was called by mcall then the\n    contents of its context field are needed to return from the mcall.\n    Fix this by saving the stack context across the calls to the other\n    goroutines.\n    \n    Reviewed-on: https://go-review.googlesource.com/41293\n\n\ncommit 43101e5956e793f1b4de05c15d7738c785e927df\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Apr 21 10:58:52 2017 +0200\n\n    os/user: use _posix_* libc functions\n    \n    libc getpwnam_r function has a different signature, we must use\n    _posix_getpwnam_r instead (by default, the pwd.h system include\n     file defines getpwnam_r as a static function calling\n    _posix_getpwnam_r, so a C program calling getpwnam_r will indeed\n    reference the _posix_getpwnam_r symbol).\n    \n    Idem for getpwuid_r, getgrnam_r and getgrgid_r.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/41334\n\n\ncommit 71e1fec4d2a536591ea6657a06916a17b5127071\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Apr 19 21:24:48 2017 -0700\n\n    runtime: don't use pointers in g_ucontext_t or stackcontext\n    \n    The g_ucontext_t type holds registers saved for a goroutine.  We have\n    to scan it for pointers, but since registers don't necessarily hold\n    pointers we have to scan it conservatively.  That means that it should\n    not have a pointer type, since the GC will always scan pointers.\n    Instead it needs special treatment to be scanned conservatively.\n    The current GC doesn't care when a pointer type holds a non-pointer,\n    but the Go 1.8 GC does.\n    \n    For the current GC this means we have to explicitly scan the\n    g_ucontext_t values in a G.\n    \n    While we're at it change stackcontext to be uintptr too.  The entries\n    in stackcontext never hold pointers that the Go GC cares about.\n    \n    Reviewed-on: https://go-review.googlesource.com/41270\n\n\ncommit eab2960aee91d3e3a6baa5b1bce01262d24c714f\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Thu Apr 20 17:08:19 2017 -0700\n\n    runtime/internal/sys: define Goexperiment\n    \n    The gc toolchain defines Goexperiment based on the environment\n    variable GOEXPERIMENT when the toolchain is built.  We just always set\n    Goexperiment to the empty string.\n    \n    Reviewed-on: https://go-review.googlesource.com/41292\n\n\ncommit be4a751943265c0637da859d15a4faf162f5c478\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Thu Apr 20 14:04:35 2017 +0200\n\n    net: sockopt implementation for AIX\n    \n    This is a copy of the Linux implementation, it allows to\n    run some simple client/server applications on AIX, while\n    the current sockopt stubs don't.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/41213\n\n\ncommit 46a669c4ca5b80fd6f6a0a42095804d9f704611d\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Mar 29 17:55:06 2017 +0200\n\n    math: fix sign for atan/expm1/log1p(-0)\n    \n    AIX libc returns +0 for atan(-0), expm1(-0) and log1p(-0),\n    while matching Go functions must return -0.\n    \n    Code courtesy of Tony Reix.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/38699\n\n\ncommit 53b0e809130038a46f0a3d2870e3905f44ab888d\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Apr 26 17:29:22 2017 +0200\n\n    runtime: fix context clobbering on AIX\n    \n    On AIX 64-bits, r13 is a pointer to thread data.\n    setcontext() overwrites r13 with the value saved by getcontext().\n    So, when a goroutine is scheduled on a new thread, r13 will point\n    to the old thread data after calling setcontext().\n    \n    Code courtesy of Damien Bergamini.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/41854\n\n\ncommit f8d5ebd71c71e6e777200530d8204b92619157f8\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Wed Apr 26 18:01:19 2017 +0200\n\n    runtime: fix wrong time calculation in semasleep\n    \n    tv_nsec is added twice when calculating the sleep end time.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/41855\n\n\ncommit ef56097f4ea848d48fbf61eba1c757fe7fce99d3\nAuthor: Matthieu Sarter <matthieu.sarter.external@atos.net>\nDate:   Fri Apr 28 10:27:32 2017 +0200\n\n    libgo: pass $(NM) value when running benchmarks\n    \n    On AIX, we need to use \"nm -B\" instead of \"nm\", to have the\n    epxected output format, so the configured $(NM) value from\n    the Makefile should be exported before running gotest, which\n    defaults to \"nm\" if $NM is not set.\n    \n    Issue golang/go#19200\n    \n    Reviewed-on: https://go-review.googlesource.com/42051\n\n\ncommit 0fb550083ae474fb964435927b899ec8e4b62771\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Wed Nov 16 21:12:53 2016 -0800\n\n    runtime: copy garbage collector from Go 1.8 runtime\n    \n    This giant patch replaces the old Go 1.4 memory allocator and garbage\n    collector with the new Go 1.8 code.  The memory allocator is fairly\n    similar, though now written in Go rather than C.  The garbage\n    collector is completely different.  It now uses ptrmask and gcprog\n    information, which requires changes in the compiler and the reflect\n    package as well as the runtime.  And, of course, the garbage collector\n    now runs concurrently with program execution.\n    \n    In the gc toolchain the garbage collector is strict and precise at all\n    levels.  In the gofrontend we do not have stack maps, so stacks, and\n    register values, are collected conservatively.  That means that an\n    old, no longer used, pointer on a stack or in a register can cause a\n    memory object to live longer than it should.  That in turns means that\n    we must disable some checks for invalid pointers in the garbage\n    collection code.  Not only can we get an invalid pointer on the stack;\n    the concurrent nature of the collector means that we can in effect\n    resurrect a block that was already unmarked but that the collector had\n    not yet gotten around to freeing, and that block can in turn point to\n    other blocks that the collector had managed to already free.  So we\n    must disable pointer checks in general.  In effect we are relying on\n    the fact that the strict pointer checks in the gc toolchain ensure\n    that the garbage collector is correct, and we just assume that it is\n    correct for the gofrontend since we are using the same code.\n    \n    Reviewed-on: https://go-review.googlesource.com/41307\n\n\ncommit a95078d501175240d095500a8c5fbfb21bec65cb\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Mon Apr 24 16:33:47 2017 -0700\n\n    libgo/Makefile: clean more files\n    \n    Fix up the mostlyclean, clean, and distclean targets to better follow\n    https://www.gnu.org/prep/standards/html_node/Standard-Targets.html.\n    \n    Reviewed-on: https://go-review.googlesource.com/41625\n\n\ncommit 5956bf1055451cf4239cdfeca259c23b1ded54d8\nAuthor: Ian Lance Taylor <iant@golang.org>\nDate:   Mon May 8 13:35:11 2017 -0700\n\n    libgo: delete goc2c\n    \n    The last .goc file has been removed, so remove goc2c.\n    \n    The goc2c program was my first contribution to the gc repository that\n    was more than 100 lines:\n    https://github.com/golang/go/commit/2b57a1124e87b0dc8bc1ff6899297b4d7d6e74f2\n    The program was used in gc for a few years under various guises but\n    was finally removed in https://golang.org/cl/132680043.  Now we can\n    remove it from gofrontend as well.\n    \n    Reviewed-on: https://go-review.googlesource.com/42911\n\n\ncommit a222e35d041de0cd42506b61c93b8209e07702b9\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Tue May 9 10:33:10 2017 -0400\n\n    compiler: set \"need_init_fn\" when adding gc root\n    \n    Variables that back slice initializers in certain cases have to be\n    added to the gc roots list, since they can be modified at runtime. The\n    code that was doing this addition did not update the flag that tracks\n    whether the package being compiled needs an initializer function,\n    which resulted in the call in question being left out of the final\n    generated code in certain cases. Fix is to change Gogo::add_gc_root()\n    to update the \"needs init\" flag.\n    \n    Reviewed-on: https://go-review.googlesource.com/43030\n\n\ncommit 822ab419bf7d1c705cdce1c12133e7a11f56be2e\nAuthor: Than McIntosh <thanm@google.com>\nDate:   Tue May 9 11:36:51 2017 -0400\n\n    compiler: fix variable context nit in write barrier generation\n    \n    Update the write barrier generation code to insure that the \"lvalue\n    context\" tag on the space var expression is set only in the case where\n    the expr feeds directly into an assignment. This is somewhat\n    counter-intuitive, but needed in the case where the backend looks at\n    context tags.\n    \n    Reviewed-on: https://go-review.googlesource.com/43031\n\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@247848 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/03118c210b2bf41242268736e16e9088293277b9"},{"sha":"380114a94a4426ce9095db7996ae280b857433c1","author":{"name":"hjl","email":"a06718a5640a8dd21346c75092b9d220d5598f07@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"Ada/x32: PR ada/80626: Correct Memory_Size\n\nX32 uses 64 as word size instead of 32.  This must not affect the\nAddress type definition which is based on Memory_Size.\n\n\tPR ada/80626\n\t* system-linux-x86.ads (Memory_Size): Use Long_Integer'Size\n\tinstead of Word_Size.\n\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@247849 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/380114a94a4426ce9095db7996ae280b857433c1"},{"sha":"23f05e90ea5b60b676c69f5bf481bfd6c3a90160","author":{"name":"uros","email":"4353b149a651e252ccaad23fae27e76cd0e2b021@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"\t* config/i386/avx512fintrin.h (_mm_mask_max_round_sd)\n\t(_mm_maskz_max_round_sd, _mm_mask_max_round_ss)\n\t(_mm_maskz_max_round_ss, _mm_mask_min_round_sd)\n\t(_mm_maskz_min_round_sd, _mm_mask_min_round_ss)\n\t(_mm_maskz_min_round_ss): New intrinsics.\n\t* config/i386/i386-builtin-types.def (V2DF, V2DF, V2DF, V2DF, UQI, INT)\n\t(V4SF, V4SF, V4SF, V4SF, UQI, INT): New function type aliases.\n\t* config/i386/i386-builtin.def (__builtin_ia32_maxsd_mask_round)\n\t(__builtin_ia32_maxss_mask_round, __builtin_ia32_minsd_mask_round)\n\t(__builtin_ia32_minss_mask_round): New builtins.\n\t* config/i386/i386.c (V2DF_FTYPE_V2DF_V2DF_V2DF_UQI_INT)\n\t(V4SF_FTYPE_V4SF_V4SF_V4SF_UQI_INT): Handle new types.\n\t* config/i386/sse.md (<sse>_vm<code><mode>3<round_saeonly_name>):\n\tRename to ...\n\t(<sse>_vm<code><mode>3<mask_name><round_saeonly_name>): ... this.\n\t(v<maxmin_float><ssescalarmodesuffix>\\t{<round_saeonly_op3>%2, %1, %0|%0, %1, %<iptr>2<round_saeonly_op3>}):\n\tChange to ...\n\t(v<maxmin_float><ssescalarmodesuffix>\\t{<round_saeonly_mask_op3>%2, %1, %0<mask_operand3>|%0<mask_operand3>, %1, %<iptr>2<round_saeonly_mask_op3>}):\n\t... this.\n\n\t* config/i386/avx512fintrin.h (_mm_mask_mul_round_sd)\n\t(_mm_maskz_mul_round_sd, _mm_mask_mul_round_ss)\n\t(_mm_maskz_mul_round_ss, _mm_mask_div_round_sd)\n\t(_mm_maskz_div_round_sd, _mm_mask_div_round_ss)\n\t(_mm_maskz_div_round_ss, _mm_mask_mul_sd, _mm_maskz_mul_sd)\n\t(_mm_mask_mul_ss, _mm_maskz_mul_ss, _mm_mask_div_sd)\n\t(_mm_maskz_div_sd, _mm_mask_div_ss, _mm_maskz_div_ss): New intrinsics.\n\t* config/i386/i386-builtin-types.def (V2DF_FTYPE_V2DF_V2DF_V2DF_UQI_INT)\n\t(V4SF_FTYPE_V4SF_V4SF_V4SF_UQI_INT): New function type aliases.\n\t* config/i386/i386-builtin.def (__builtin_ia32_divsd_mask_round)\n\t(__builtin_ia32_divss_mask_round, __builtin_ia32_mulsd_mask_round)\n\t(__builtin_ia32_mulss_mask_round): New builtins.\n\t* config/i386/i386.c (V2DF_FTYPE_V2DF_V2DF_V2DF_UQI_INT)\n\t(V4SF_FTYPE_V4SF_V4SF_V4SF_UQI_INT): Handle new types.\n\t* config/i386/sse.md (<sse>_vm<multdiv_mnemonic><mode>3<round_name>):\n\tRename to ...\n\t(<sse>_vm<multdiv_mnemonic><mode>3<mask_name><round_name>): ... this.\n\t(v<multdiv_mnemonic><ssescalarmodesuffix>\\t{<round_op3>%2, %1, %0|%0, %1, %<iptr>2<round_op3>}):\n\tChange to ...\n\t(v<multdiv_mnemonic><ssescalarmodesuffix>\\t{<round_mask_op3>%2, %1, %0<mask_operand3>|%0<mask_operand3>, %1, %<iptr>2<round_mask_op3>}):\n\t... this.\n\n\t* config/i386/avxintrin.h (_mm256_set_m128, _mm256_set_m128d)\n\t(_mm256_set_m128i, _mm256_setr_m128, _mm256_setr_m128d)\n\t(_mm256_setr_m128i): New intrinsics.\n\n\t* config/i386/avx512fintrin.h (_mm_mask_rcp14_sd)\n\t(_mm_maskz_rcp14_sd, _mm_mask_rcp14_ss)\n\t(_mm_maskz_rcp14_ss): New intrinsics.\n\t* config/i386/i386-builtin.def (__builtin_ia32_rcp14sd_mask)\n\t(__builtin_ia32_rcp14ss_mask): New builtins.\n\t* config/i386/sse.md (srcp14<mode>_mask): New pattern.\n\ntestsuite/ChangeLog:\n\n\t* gcc.target/i386/avx512f-vmaxsd-1.c (_mm_mask_max_round_sd)\n\t(_mm_maskz_max_round_sd): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vmaxsd-2.c: New.\n\t* gcc.target/i386/avx512f-vmaxss-1.c (_mm_mask_max_round_ss)\n\t(_mm_maskz_max_round_ss): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vmaxss-2.c: New.\n\t* gcc.target/i386/avx512f-vminsd-1.c (_mm_mask_min_round_sd)\n\t(_mm_maskz_min_round_sd): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vminsd-2.c: New.\n\t* gcc.target/i386/avx512f-vminss-1.c (_mm_mask_min_round_ss)\n\t(_mm_maskz_min_round_ss): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vminss-2.c: New.\n\t* gcc.target/i386/avx-1.c (__builtin_ia32_maxsd_mask_round)\n\t(__builtin_ia32_maxss_mask_round, __builtin_ia32_minsd_mask_round)\n\t(__builtin_ia32_minss_mask_round): Test new builtins.\n\t* gcc.target/i386/sse-13.c: Ditto.\n\t* gcc.target/i386/sse-23.c: Ditto.\n\t* gcc.target/i386/sse-14.c (_mm_maskz_max_round_sd)\n\t(_mm_maskz_max_round_ss, _mm_maskz_min_round_sd)\n\t(_mm_maskz_min_round_ss, _mm_mask_max_round_sd)\n\t(_mm_mask_max_round_ss, _mm_mask_min_round_sd)\n\t(_mm_mask_min_round_ss): Test new intrinsics.\n\t* gcc.target/i386/testround-1.c: Ditto.\n\n\t* gcc.target/i386/avx512f-vdivsd-1.c (_mm_mask_div_sd)\n\t(_mm_maskz_div_sd, _mm_mask_div_round_sd)\n\t(_mm_maskz_div_round_sd): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vdivsd-2.c: New.\n\t* gcc.target/i386/avx512f-vdivss-1.c (_mm_mask_div_ss)\n\t(_mm_maskz_div_ss, _mm_mask_div_round_ss)\n\t(_mm_maskz_div_round_ss): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vdivss-2.c: New.\n\t* gcc.target/i386/avx512f-vmulsd-1.c (_mm_mask_mul_sd)\n\t(_mm_maskz_mul_sd, _mm_mask_mul_round_sd)\n\t(_mm_maskz_mul_round_sd): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vmulsd-2.c: New.\n\t* gcc.target/i386/avx512f-vmulss-1.c (_mm_mask_mul_ss)\n\t(_mm_maskz_mul_ss, _mm_mask_mul_round_ss)\n\t(_mm_maskz_mul_round_ss): Test new intrinsics.\n\t* gcc.target/i386/avx512f-vmulss-2.c: New.\n\t* gcc.target/i386/avx-1.c (__builtin_ia32_divsd_mask_round)\n\t(__builtin_ia32_divss_mask_round, __builtin_ia32_mulsd_mask_round)\n\t(__builtin_ia32_mulss_mask_round): Test new builtins.\n\t* gcc.target/i386/sse-13.c: Ditto.\n\t* gcc.target/i386/sse-23.c: Ditto.\n\t* gcc.target/i386/sse-14.c (_mm_maskz_div_round_sd)\n\t(_mm_maskz_div_round_ss, _mm_maskz_mul_round_sd)\n\t(_mm_maskz_mul_round_ss): Test new intrinsics.\n\t* gcc.target/i386/testround-1.c: Ditto.\n\n\t* gcc.target/i386/avx-vinsertf128-256-1: Test new intrinsics.\n\t* gcc.target/i386/avx-vinsertf128-256-2: Ditto.\n\t* gcc.target/i386/avx-vinsertf128-256-3: Ditto.\n\n\t* gcc.target/i386/avx512f-vrcp14sd-1.c: Test new intrinsics.\n\t* gcc.target/i386/avx512f-vrcp14sd-2.c: Ditto.\n\t* gcc.target/i386/avx512f-vrcp14ss-1.c: Ditto.\n\t* gcc.target/i386/avx512f-vrcp14ss-2.c: Ditto.\n\n\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@247851 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/23f05e90ea5b60b676c69f5bf481bfd6c3a90160"},{"sha":"01b24b6e14719f78b6a081a08ac94c80cf3eada3","author":{"name":"wschmidt","email":"8650395859f1369ba83ea74c3e3839ee22d2539f@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"[gcc]\n\n2017-05-10  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>\n\n\t* config/rs6000/rs6000.c (altivec_init_builtins): Define POWER8\n\tbuilt-ins for vec_xl and vec_xst with short and char pointer\n\targuments.\n\n[gcc/testsuite]\n\n2017-05-10  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>\n\n\t* gcc.target/powerpc/p8-vec-xl-xst.c: New file.\n\n\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@247854 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/01b24b6e14719f78b6a081a08ac94c80cf3eada3"}]}
{"actor":{"display_login":"kraj"}}