From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-502003-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 92623 invoked by alias); 30 May 2019 20:49:26 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 92615 invoked by uid 89); 30 May 2019 20:49:25 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:423
X-HELO: mail-vs1-f48.google.com
Received: from mail-vs1-f48.google.com (HELO mail-vs1-f48.google.com) (209.85.217.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 30 May 2019 20:49:24 +0000
Received: by mail-vs1-f48.google.com with SMTP id t20so2715042vso.2        for <gcc-patches@gcc.gnu.org>; Thu, 30 May 2019 13:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=sifive.com; s=google;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=RInPqf+A5YAL83Oluuawp8QremnqvM6LSmA7iJl5F40=;        b=Uel7Ll9OP5C6AxU5SfHf4lD+M1vGwArNVpHax8sQDy97Qx3QL+svnCEjkB/9TA6h2p         hn1DC33vx2Zmvq2dRNeRK/cYb/Fz8yAQRlMGofDIU8JnCyIaB+sX8VwXB37Q+Edejbl5         C7sw5e/27z279XxB7ne9ufBewpvVSnkWDtEnqILofWdXcqFouWdbn0nRAzmy5sSDbTek         THaiUGr8khu4N6QpsabtVpKpgP3F6ubKgx0dKiMsbluCyl+Gi/0NwBxnQFvdx4lsgZKc         my7URKenwFX2LmPNk4UZ51C46tz4vSHTrY4RzUaRKDZF9NZ1u0ORE9zyMDkyg238MBRW         zt9g==
MIME-Version: 1.0
References: <CAOyqgcUfhNqUfBtRroHB5SyKeRn0=faPVO7KhJsF8QLa1rKH+w@mail.gmail.com> <87a7fibpms.fsf@igel.home> <CAFyWVaY8aMmhmnWpoGdywaeEhiXmSUe8qqha+HhvbxYHhUnisQ@mail.gmail.com> <CAHpjNSKtyody2NspEbzE47JOsRdb5OGSqK3DCVqo-H+d2ny=pA@mail.gmail.com> <CAOyqgcWUovBynsiQuquxgeZy-cdTfGdZxZou8A4yH-q9-dD_JA@mail.gmail.com>
In-Reply-To: <CAOyqgcWUovBynsiQuquxgeZy-cdTfGdZxZou8A4yH-q9-dD_JA@mail.gmail.com>
From: Jim Wilson <jimw@sifive.com>
Date: Thu, 30 May 2019 20:50:00 -0000
Message-ID: <CAFyWVaa9aOc5D6rfKo5Ktt7RmJMYdH7v+CWMoNkggQK+BYDFgA@mail.gmail.com>
Subject: Re: [gofrontend-dev] Re: Go patch committed: Intrinsify runtime/internal/atomic functions
To: Ian Lance Taylor <iant@golang.org>
Cc: Cherry Zhang <cherryyz@google.com>, Andreas Schwab <schwab@linux-m68k.org>, 	gcc-patches <gcc-patches@gcc.gnu.org>, gofrontend-dev <gofrontend-dev@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-05/txt/msg02056.txt.bz2

On Wed, May 22, 2019 at 6:41 PM Ian Lance Taylor <iant@golang.org> wrote:
> Jim, you can go ahead and commit that patch with a ChangeLog entry.
> (The files in go/gcc but not in go/gcc/gofrontend) are under normal
> GCC rules.)  Thanks.

OK.  Committed.  I did an x86_64-linux go build and check to make sure
I didn't break that.

Jim