This is the mail archive of the
mailing list for the GCC project.
Re: Question about Gimple FE
- From: Jeff Law <law at redhat dot com>
- To: Trevor Saunders <tbsaunde+mozilla at tbsaunde dot org>, Richard Biener <richard dot guenther at gmail dot com>
- Cc: xue yinsong <xyshh94225 at hotmail dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 02 Apr 2015 15:14:54 -0600
- Subject: Re: Question about Gimple FE
- Authentication-results: sourceware.org; auth=none
- References: <BLU436-SMTP393D735E667D7744698A4D85080 at phx dot gbl> <CAFiYyc0ukmm0w+YPQ1QOV2Vw3euPmVZR2MLHsjc25XB9T0ds8w at mail dot gmail dot com> <20150331153439 dot GC4210 at tsaunders-iceball dot corp dot tor1 dot mozilla dot com>
On 03/31/2015 09:34 AM, Trevor Saunders wrote:
David has some code that allows creation of gimple on the fly and
feeding it to a pass which is obviously designed with unit testing in mind.
On Thu, Mar 26, 2015 at 03:15:22PM +0100, Richard Biener wrote:
On Thu, Mar 26, 2015 at 2:31 PM, xue yinsong <email@example.com> wrote:
I think the gimple front end project would be quite useful to gcc so Iâd like to do work on it this summer.
The problem is, it seems the GIMPLE front end project hasnât been active for some time
and Diego Novillo told me it may not even make sense to use the same codebase, but start from scratch.
Iâm not sure if I should pick it up where it left off or write another one from scratch
Could you give me some advice?
I don't know the current codebase at all (unfortunately). I think it
is useful to get yourself familiarized
with it even if you start from scratch as it will get you to learn
something about GIMPLE and about
writing a frontend.
Note that LTO support already is able to output everything needed to
re-create GIMPLE thus from
there you can also learn what is required to populate a GIMPLE
representation. And LTO support
might be used to create output that can be read by the GIMPLE frontend
- the whole project
feels like finding a textual form of the LTO bytecode (in some way).
I think its part being able to convert LTO byte code to text, and part
refactoring byte code reading / writing such that we can do things like
read in byte code run a single pass and then dump the resulting byte
code. I suppose in a sense you can probably already do that with lto1
and -r, but that's not exactly straight forward.