From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108812 invoked by alias); 20 Sep 2019 19:17:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 108799 invoked by uid 89); 20 Sep 2019 19:17:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=H*i:sk:44a0bdc, H*f:sk:44a0bdc, H*c:alternative X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Sep 2019 19:17:09 +0000 Received: from mail-ot1-f71.google.com (mail-ot1-f71.google.com [209.85.210.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 54EC681F18 for ; Fri, 20 Sep 2019 19:17:08 +0000 (UTC) Received: by mail-ot1-f71.google.com with SMTP id a8so4258279otd.7 for ; Fri, 20 Sep 2019 12:17:08 -0700 (PDT) MIME-Version: 1.0 References: <494fcfcb.4f376.16d25f2d9b7.Coremail.jianbinfang@yeah.net> <44a0bdc2-c3fe-3d85-e431-770722116982@redhat.com> In-Reply-To: <44a0bdc2-c3fe-3d85-e431-770722116982@redhat.com> From: Jason Merrill Date: Fri, 20 Sep 2019 19:17:00 -0000 Message-ID: Subject: Re: taking OpenCL C as a built-in lang of GCC? To: Jeff Law Cc: Jianbin Fang , gcc Mailing List , gcc-help@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00161.txt.bz2 On Fri, Sep 20, 2019, 1:10 PM Jeff Law wrote: > On 9/12/19 8:48 AM, Jianbin Fang wrote: > > Hello Guys, > > > > > > > > I am working on OpenCL for a couple of years, and would like to ask, > > as for GCC, why not taking OpenCL C as a built-in language in its > > front-end? > There's no inherent reason why we don't support OpenCL C. Someone would > just need to write a suitable front-end for GCC and contribute it. > Or a patch to add it to the C front end. >