public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Grigori Fursin" <grigori.fursin@inria.fr>
To: <clattner@apple.com>
Cc: <ubizjak@gmail.com>, 	<gcc@gcc.gnu.org>,
		"Zbigniew Chamski" <zbigniew.chamski@gmail.com>,
		"Andy Nisbet" <A.Nisbet@mmu.ac.uk>, 	<baldrick@free.fr>,
		<espindola@google.com>, 	<Albert.Cohen@inria.fr>,
		"Ayal Zaks" <ZAKS@il.ibm.com>
Subject: Re: LLVM as a gcc plugin?
Date: Fri, 05 Jun 2009 09:55:00 -0000	[thread overview]
Message-ID: <4a28eb9b.07a5660a.3791.270f@mx.google.com> (raw)

Hi guys,

Just saw this discussion so wanted to mention that we at HiPEAC are now interested
to use both GCC as static compiler and LLVM as run-time infrastructure for research
and several colleagues wanted to port ICI framework (the recent release is based
on the "official" gcc plugin branch) to LLVM. We want to have both official
gcc plugins and ICI addition on top of it since we have a relatively large community
already around those tools and ICI plugins, and additional tools for automatic program 
optimization.

I will unlikely be involved in that now because I just don't have time so I CCed
this email to Andy Nisbet who has been interested to provide plugin system for LLVM,
Zbigniew Chamski who supports ICI for GCC and also Albert Cohen and Ayal Zaks 
who are also coordinating those activities within HiPEAC. 

The idea is to make GCC and LLVM more attractive to the researchers (i.e. that it's
easy to use compilers without knowing internals much) so that research ideas could
go back to the compilers much faster improving GCC and LLVM ...

Cheers,
Grigori


> On Jun 3, 2009, at 11:30 PM, Uros Bizjak wrote:
>
>    Hello!
>
>    Some time ago, there was a discussion about integrating LLVM and GCC
>    [1]. However, with plugin infrastructure in place, could LLVM be
>    plugged into GCC as an additional optimization plugin?
>
>
>    [1] http://gcc.gnu.org/ml/gcc/2005-11/msg00888.html 
>
>
> Hi Uros,
>
> I'd love to see this, but I can't contribute to it directly. I think the plugin interfaces would
need small 
> extensions, but there are no specific technical issues preventing it from happening. LLVM has
certainly progressed a 
> lot since that (really old) email went out :)
>
> -Chris

             reply	other threads:[~2009-06-05  9:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  9:55 Grigori Fursin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-05 10:41 Andrew  Nisbet
2009-06-05 10:43 ` Steven Bosscher
2009-06-05 16:49   ` Chris Lattner
2009-06-05 21:06     ` Joe Buck
2009-06-08  1:10       ` Rafael Espindola
2009-06-08 10:41         ` Steven Bosscher
2009-06-08 13:28           ` Rafael Espindola
2009-06-04  6:30 Uros Bizjak
2009-06-04  6:39 ` Chris Lattner
2009-06-04  6:59   ` Miles Bader
2009-06-04 16:06     ` Chris Lattner
2009-06-04 10:14   ` Rafael Espindola
2009-06-04 10:21     ` Steven Bosscher
2009-06-04 10:33       ` Rafael Espindola
2009-06-04 16:12       ` Chris Lattner
2009-06-04 19:25     ` Duncan Sands
2009-06-04 20:56       ` Ian Lance Taylor
2009-06-04  7:36 ` Duncan Sands

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=4a28eb9b.07a5660a.3791.270f@mx.google.com \
    --to=grigori.fursin@inria.fr \
    --cc=A.Nisbet@mmu.ac.uk \
    --cc=Albert.Cohen@inria.fr \
    --cc=ZAKS@il.ibm.com \
    --cc=baldrick@free.fr \
    --cc=clattner@apple.com \
    --cc=espindola@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ubizjak@gmail.com \
    --cc=zbigniew.chamski@gmail.com \
    /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).