From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-426876-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 39472 invoked by alias); 9 May 2016 13:39:52 -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 39447 invoked by uid 89); 9 May 2016 13:39:52 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:536
X-HELO: mail-qk0-f195.google.com
Received: from mail-qk0-f195.google.com (HELO mail-qk0-f195.google.com) (209.85.220.195) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 09 May 2016 13:39:50 +0000
Received: by mail-qk0-f195.google.com with SMTP id l68so12207940qkf.3        for <gcc-patches@gcc.gnu.org>; Mon, 09 May 2016 06:39:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:sender:subject:to:references:from:message-id         :date:user-agent:mime-version:in-reply-to:content-transfer-encoding;        bh=3RW1/xYgHeGKnKQWdRPr6aKxsQB1UooJudd8D4UkITw=;        b=VVe7xEwu54TCvhcYupG43GVi0hSvceq0Yg9azqBdnkwzwtbUFwKKOm4EB/bfrMpFH8         Kodk2DmpSoKF8YViNO1vks9rcIc7UPuWqgLU2sbx8YvQ8I0f6Wt+16Nbpn+nRB62WguW         pKVSRTHscCBwWeOlmgs9z73yD1Rk/YM6saxlRUwl/QvW8Vt9g+77kepMMtWlFKJx1xjl         AOtFQfTck5NDom54s5lZWUk8TydY0iCJtN/waZyYpuJBI8IRcSJtZojSi3oJ3cT9JPqP         nFNWjZ4XAg2FfiI50NARgJrBwWJB0jkILwYw83GUxfNLZVuLfJp7IBZQpUMexJoe0x1y         gVaA==
X-Gm-Message-State: AOPr4FXTD1JaNaDKAZztx1pMZzDzmA02bDH/4/hiWSIhWV32VOnL3HfJexkjyk4WAmqzlA==
X-Received: by 10.55.103.68 with SMTP id b65mr37076494qkc.22.1462801188800;        Mon, 09 May 2016 06:39:48 -0700 (PDT)
Received: from ?IPv6:2601:181:c003:1930:a2a8:cdff:fe3e:b48? ([2601:181:c003:1930:a2a8:cdff:fe3e:b48])        by smtp.googlemail.com with ESMTPSA id 94sm11838799qgl.11.2016.05.09.06.39.47        (version=TLSv1/SSLv3 cipher=OTHER);        Mon, 09 May 2016 06:39:48 -0700 (PDT)
Subject: Re: [PATCH v2] add support for placing variables in shared memory
To: Alexander Monakov <amonakov@ispras.ru>, gcc-patches@gcc.gnu.org
References: <alpine.LNX.2.20.1604201957570.14803@monopod.intra.ispras.ru> <alpine.LNX.2.20.1605061958430.20406@monopod.intra.ispras.ru>
From: Nathan Sidwell <nathan@acm.org>
Message-ID: <2c458247-ff60-6c38-e749-9658dbeb93ed@acm.org>
Date: Mon, 09 May 2016 13:39:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <alpine.LNX.2.20.1605061958430.20406@monopod.intra.ispras.ru>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-05/txt/msg00625.txt.bz2

On 05/06/16 13:11, Alexander Monakov wrote:
> Allow using __attribute__((shared)) to place static variables in '.shared'
> memory space.
>
> Changes in v2:
> - reword diagnostic message in nvptx_handle_shared_attribute to follow other
>   backends ("... attribute not allowed with auto storage class");
> - reject explicit initialization of ".shared" memory variables;
> - add testcases.

thanks, this is ok to commit now -- I see no reason why it needs to wait.

nathan