public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, gofrontend-dev@googlegroups.com
Subject: Re: libgo patch committed: Update to 1.11 release
Date: Wed, 26 Sep 2018 15:16:00 -0000	[thread overview]
Message-ID: <CAMe9rOoUcdVUX-B1xDbNU9001ttr+N7mCz2kG5Dj8iOjdTJ=DA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOr6p-qX8tVFUZ9g5G0VMbUf7Gw8XjTFyM68B-GzHTyuww@mail.gmail.com>

On Wed, Sep 26, 2018 at 7:50 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, Sep 24, 2018 at 2:46 PM, Ian Lance Taylor <iant@golang.org> wrote:
>> I've committed a patch to update libgo to the 1.11 release.  As usual
>> for these updates, the patch is too large to attach to this e-mail
>> message.  I've attached some of the more relevant directories.  This
>> update required some minor patches to the gotools directory and the Go
>> testsuite, also included here.  Bootstrapped and ran Go testsuite on
>> x86_64-pc-linux-gnu.  Committed to mainline.
>>
>> Ian
>>
>> 2018-09-24  Ian Lance Taylor  <iant@golang.org>
>>
>> * Makefile.am (mostlyclean-local): Run chmod on check-go-dir to
>> make sure it is writable.
>> (check-go-tools): Likewise.
>> (check-vet): Copy internal/objabi to check-vet-dir.
>> * Makefile.in: Rebuild.
>
> When building with -mx32, I got
>
> /export/gnu/import/git/sources/gcc/libgo/go/runtime/malloc.go:309:44:
> error: integer constant overflow
> 309 |  arenaBaseOffset uintptr = sys.GoarchAmd64 * (1 << 47)
>     |                                            ^
>

This seems to work:

diff --git a/libgo/go/runtime/malloc.go b/libgo/go/runtime/malloc.go
index ac4759ffbf1..c3445387057 100644
--- a/libgo/go/runtime/malloc.go
+++ b/libgo/go/runtime/malloc.go
@@ -306,7 +306,7 @@ const (
   //
   // On other platforms, the user address space is contiguous
   // and starts at 0, so no offset is necessary.
-  arenaBaseOffset uintptr = sys.GoarchAmd64 * (1 << 47)
+  arenaBaseOffset uintptr = _64bit * sys.GoarchAmd64 * (1 << 47)

   // Max number of threads to run garbage collection.
   // 2, 3, and 4 are all plausible maximums depending


-- 
H.J.

  reply	other threads:[~2018-09-26 15:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 21:49 Ian Lance Taylor
2018-09-25  7:06 ` Andreas Schwab
2018-09-25  7:57 ` Andreas Schwab
2018-09-25  9:05   ` Andreas Schwab
2018-09-25 14:39     ` Ian Lance Taylor
2018-09-25 13:10 ` Rainer Orth
2018-09-25 13:34   ` Rainer Orth
2018-09-26  5:04     ` Ian Lance Taylor
2018-09-26  8:55       ` Rainer Orth
2018-09-26  7:57 ` Andreas Schwab
2018-09-26  8:59   ` Rainer Orth
2018-09-26 12:54     ` Ian Lance Taylor
2018-09-26 11:12 ` Andreas Schwab
2018-09-26 12:49   ` Ian Lance Taylor
2018-10-01 20:18   ` Ian Lance Taylor
2018-09-26 14:52 ` H.J. Lu
2018-09-26 15:16   ` H.J. Lu [this message]
2018-10-01 20:28   ` Ian Lance Taylor
2018-10-01 20:59     ` H.J. Lu
2018-10-02  0:06       ` H.J. Lu
2018-10-02  0:59         ` Ian Lance Taylor
2018-10-02  2:37           ` H.J. Lu
2018-10-02  4:09             ` Ian Lance Taylor
2018-10-03 14:09               ` H.J. Lu
2018-10-03 22:04           ` Ian Lance Taylor
2018-09-28 14:28 ` Rainer Orth
2018-10-02 17:13   ` Ian Lance Taylor
2018-10-04 12:05     ` Rainer Orth
2018-09-26  7:58 Uros Bizjak
2018-09-26 15:22 ` Ian Lance Taylor
2018-09-27 20:26   ` Uros Bizjak
2018-09-28  7:13 ` Uros Bizjak
2018-10-02 15:13   ` 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='CAMe9rOoUcdVUX-B1xDbNU9001ttr+N7mCz2kG5Dj8iOjdTJ=DA@mail.gmail.com' \
    --to=hjl.tools@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).