From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4772 invoked by alias); 6 Aug 2015 19:51:28 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 4763 invoked by uid 89); 6 Aug 2015 19:51:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f181.google.com Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 06 Aug 2015 19:51:26 +0000 Received: by wijp15 with SMTP id p15so35478940wij.0 for ; Thu, 06 Aug 2015 12:51:23 -0700 (PDT) X-Received: by 10.180.94.7 with SMTP id cy7mr9092896wib.79.1438890683409; Thu, 06 Aug 2015 12:51:23 -0700 (PDT) Received: from [192.168.10.82] (11.52.broadband16.iol.cz. [90.183.52.11]) by smtp.googlemail.com with ESMTPSA id ft5sm4884597wib.4.2015.08.06.12.51.21 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Aug 2015 12:51:22 -0700 (PDT) Subject: Re: [gomp4] Redesign oacc_parallel launch API To: Cesar Philippidis , GCC Patches References: <55B7B332.1010603@acm.org> <55C38C5D.6040602@mentor.com> Cc: Jakub Jelinek , Thomas Schwinge From: Nathan Sidwell Message-ID: <55C3BAB8.2090201@acm.org> Date: Thu, 06 Aug 2015 19:51:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55C38C5D.6040602@mentor.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-08/txt/msg00369.txt.bz2 On 08/06/15 18:33, Cesar Philippidis wrote: > Looking at set_oacc_fn_attrib, it appears that const values are also > considered dynamic. See the attached test case more more info. Is that > the expected behavior? If not, I could take a look at this after I > finished my reduction patch. It's annoying that the offload call is happening too early for that kind of constant propagation. But I guess it might have been propagated by the time we get to oacc_xform. And hence that could optimize there. Anyway, a thing to notice but not get distracted by. nathan