From: "Jianbin Fang" <jianbinfang@yeah.net>
To: gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: taking OpenCL C as a built-in lang of GCC?
Date: Thu, 12 Sep 2019 14:49:00 -0000 [thread overview]
Message-ID: <494fcfcb.4f376.16d25f2d9b7.Coremail.jianbinfang@yeah.net> (raw)
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?
As we know, most OpenCL kernel compilers are built based on Clang/LLVM, and now, Clang has taken the OpenCL C language as one of its built-in languages. On the other hand, I found no OpenCL implementations which are based on GCC. Do you have any idea of the reasons?
I have this question because some devices may not have LLVM backends, but only have their backends in GCC. In such a case, a natural way is to add a new font-end into GCC, and build a kernel compiler based on the GCC compiling passes. What are the difficulties behind this idea?
Regards,
Jianbin
next reply other threads:[~2019-09-12 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 14:49 Jianbin Fang [this message]
2019-09-12 14:59 ` Jonathan Wakely
2019-09-20 17:10 ` Jeff Law
2019-09-20 19:17 ` Jason Merrill
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=494fcfcb.4f376.16d25f2d9b7.Coremail.jianbinfang@yeah.net \
--to=jianbinfang@yeah.net \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).