From: Rafael Espindola <espindola@google.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Joe Buck <Joe.Buck@synopsys.com>,
Chris Lattner <clattner@apple.com>,
Andrew Nisbet <A.Nisbet@mmu.ac.uk>,
"grigori.fursin@inria.fr" <grigori.fursin@inria.fr>,
"baldrick@free.fr" <baldrick@free.fr>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"ubizjak@gmail.com" <ubizjak@gmail.com>,
"zbigniew.chamski@gmail.com" <zbigniew.chamski@gmail.com>,
"ZAKS@il.ibm.com" <ZAKS@il.ibm.com>,
"Albert.Cohen@inria.fr" <Albert.Cohen@inria.fr>
Subject: Re: LLVM as a gcc plugin?
Date: Mon, 08 Jun 2009 13:28:00 -0000 [thread overview]
Message-ID: <38a0d8450906080628n9533afcjae087ac9baada124@mail.gmail.com> (raw)
In-Reply-To: <571f6b510906080341l37bc582fq1f7015743fa74c0@mail.gmail.com>
> I'd turn that around: There is already a version of LLVM that uses
> GCC. I don't see any way in which the FSF GCC benefits from this. And
> since this list concerns the FSF GCC...
That is not a valid turn around. We know that the existing LLVM can handle
this. We are not sure if the existing plugin infrastructure can.
That also goes to the more general question "should plugin development be
discussed on this list?". One of the main uses of plugins will probably be
adding features that are not of interest to GCC in general.
> Ciao!
> Steven
>
Cheers,
--
Rafael Avila de Espindola
Google | Gordon House | Barrow Street | Dublin 4 | Ireland
Registered in Dublin, Ireland | Registration Number: 368047
next prev parent reply other threads:[~2009-06-08 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-05 9:55 Grigori Fursin
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=38a0d8450906080628n9533afcjae087ac9baada124@mail.gmail.com \
--to=espindola@google.com \
--cc=A.Nisbet@mmu.ac.uk \
--cc=Albert.Cohen@inria.fr \
--cc=Joe.Buck@synopsys.com \
--cc=ZAKS@il.ibm.com \
--cc=baldrick@free.fr \
--cc=clattner@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=grigori.fursin@inria.fr \
--cc=stevenb.gcc@gmail.com \
--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).