public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Cherry Zhang via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	Ian Lance Taylor <iant@golang.org>,
		gcc-patches <gcc-patches@gcc.gnu.org>,
	gofrontend-dev <gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Cheaper context switch on x86_64
Date: Mon, 03 Jun 2019 16:44:00 -0000	[thread overview]
Message-ID: <CAHpjNSL84LK02h8zfb9Fw+nnLpZgEKj+0+015Q7GJ=Pf6oKTJw@mail.gmail.com> (raw)
In-Reply-To: <20190603160007.GQ19695@tucnak>

On Mon, Jun 3, 2019 at 12:00 PM Jakub Jelinek <jakub@redhat.com> wrote:

> On Mon, Jun 03, 2019 at 05:51:26PM +0200, Thomas Schwinge wrote:
> > Hi!
> >
> > On Fri, 31 May 2019 10:56:43 -0700, Ian Lance Taylor <iant@golang.org>
> wrote:
> > > This libgo patch by Cherry Zhang implements cheaper goroutine context
> > > switches on x86_64 GNU/Linux.  [...]
> >
> > > Bootstrapped and tested on x86_64-pc-linux-gnu.  Committed to mainline.
> >
> > > --- libgo/runtime/go-context.S      (nonexistent)
> > > +++ libgo/runtime/go-context.S      (working copy)
> >
> > > +   andq    $~0xfULL, %rdx
> >
> > I run into:
> >
> >     [...]/libgo/runtime/go-context.S: Assembler messages:
> >     [...]/libgo/runtime/go-context.S:60: Error: junk `ULL' after
> expression
> >     make[4]: *** [runtime/go-context.lo] Error 1
> >
> > ... with (admittedly somewhat old) Binutils:
> >
> >     $ as --version | head -n 2
> >     GNU assembler (GNU Binutils for Ubuntu) 2.22.90.20120924
> >     Copyright 2012 Free Software Foundation, Inc.
>
> As andq immediate is just 32-bit, I'd say using $~0xf or $-16 instead of
> $~0xfULL is the right fix.
>

Sorry for the breakage. Send https://golang.org/cl/180217 dropping the ULL
suffix as you suggested.

Thanks,
Cherry

  reply	other threads:[~2019-06-03 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 18:20 Ian Lance Taylor
2019-06-03 15:51 ` Thomas Schwinge
2019-06-03 16:00   ` Jakub Jelinek
2019-06-03 16:44     ` Cherry Zhang via gcc-patches [this message]
2019-06-03 20:07       ` 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='CAHpjNSL84LK02h8zfb9Fw+nnLpZgEKj+0+015Q7GJ=Pf6oKTJw@mail.gmail.com' \
    --to=gcc-patches@gcc.gnu.org \
    --cc=cherryyz@google.com \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=iant@golang.org \
    --cc=jakub@redhat.com \
    --cc=thomas@codesourcery.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).