public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* taking OpenCL C as a built-in lang of GCC?
@ 2019-09-12 14:49 Jianbin Fang
  2019-09-12 14:59 ` Jonathan Wakely
  2019-09-20 17:10 ` Jeff Law
  0 siblings, 2 replies; 4+ messages in thread
From: Jianbin Fang @ 2019-09-12 14:49 UTC (permalink / raw)
  To: gcc, gcc-help

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-09-20 19:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-12 14:49 taking OpenCL C as a built-in lang of GCC? Jianbin Fang
2019-09-12 14:59 ` Jonathan Wakely
2019-09-20 17:10 ` Jeff Law
2019-09-20 19:17   ` Jason Merrill

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).