> ----- Original Message ----- > From: Basile Starynkevitch <bas...@starynkevitch.net> > To: "Levon Haykazyan" <le...@rock.com> > Cc: gcc@gcc.gnu.org > Subject: Re: Oberon-2 front-end as a GSoC project > Date: Wed, 6 Apr 2011 21:19:05 +0200 > > > On Wed, 06 Apr 2011 19:07:26 +0000 > "Levon Haykazyan" <le...@rock.com> wrote: > [citing me Basile] > > > > You probably could write the front-end part of your compiler in Oberon, > > > and generate Gimple representation (perhaps even in textual form, since > > > some people are working on a Gimple "front-end"). You then win all the > > > optimization & code generation abilities of GCC. > [...] > > That is actually a very good suggestion, thank you. I'll think about > > implementing a GIMPLE back-end. > > To be clear, I am suggesting you to use the existing GCC back-end, and > to generate, from inside your Oberon front-end, the GIMPLE code. So > your Oberon compiler is (grossly) made of your Oberon front-end > generating Gimple (either in textual form, or by calling the relevant > GCC API to build GIMPLE representation in memory, calling GCC C > functions related to GIMPLE from your Oberon front-end) and of the > existing gcc/libbackend.a of GCC. Of course, the evil is in the > details. > > What you will code cannot be said "a Gimple back-end" since this > already exists (as gcc/libbackend.a) in GCC. > > Regards. > -- > Basile STARYNKEVITCH http://starynkevitch.net/Basile/ > email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 > 8, rue de la Faiencerie, 92340 Bourg La Reine, France > *** opinions {are only mine, sont seulement les miennes} ***
> Hi Basile, What I meant was a GIMPLE back-end for my compiler. I decided I want a simple native code generator, after all this is a learning experience for me. If the project grows serious I'll consider using gcc or LLVM back-ends. Thanks again everyone for suggestions. Kind regards, Levon -- You Rock! Your E-Mail Should Too! Signup Now at Rock.com and get 2GB of Storage! http://connections.rock.com/user/displayUserRegisterPage.kickAction?as=116748&STATUS=MAIN
