|porting gcc email@example.com (2000-09-15)|
|Re: porting gcc firstname.lastname@example.org (Jeff Sturm) (2000-09-17)|
|Re: porting gcc email@example.com (Michael A. Sewell) (2000-09-17)|
|Re: porting gcc firstname.lastname@example.org (2000-09-17)|
|Re: porting gcc email@example.com (2000-09-28)|
|Re: porting gcc firstname.lastname@example.org (Tom Payne) (2000-10-08)|
|From:||email@example.com (Juergen Fischer)|
|Date:||28 Sep 2000 17:39:41 -0400|
thank you all for providing URLs.
Jeff Sturm <firstname.lastname@example.org> wrote:
> Juergen Fischer wrote:
> > - actually I want g++. assuming a g++ port, is the result any use for
> > porting gcc? are they "RTL-compatible" ?
> Err... why not? Both gcc and g++ generate RTL from syntax trees, and
> they share the same backend.
I heard about the possibility of a c++ -> c translator. however my
theory is that c++ exceptions need capabilities beyond stack
operations expressible in C, which is why I thought it might be
possible RTL had to be extended in order to run c++. this was the idea
behind the question.
Now As RTL turns out to be another level than I had thought of, the
question is obsolete.
> > - I need win32 executable gcc to start with.
> Get the mingw ports at http://www.mingw.org/.
Oh, I bumped into cygnus executable, but its bin/ contains a
mingwc10.dll ... but ld can't find crt0.o even though it is in
> > actually my first step problem is to download the right set of
> > source/executable packages to start with. and the "how to port gcc"
> > manual I heard about but searchengines don't find...
> This and many other links are available from the main GCC site:
I had a quick glance at it. mhm looks like lisp.
seems to be a language about pointer = 32bit register.
whilst I, knowing nothing, had expected to be presented some graphs...
then writing C code digging node structs (that keep yummy information
such as char*, I guess that's what you called syntax trees). this is
somewhere in C frontend, and I guess it would have made more
complicated to make this stage the backend interface, especially when
thinking about other language frontents. otoh I wonder whether there
is a machine that can (reasonably) run C, but can't run some of said
languages. probably it would actually not make problems to frontends,
but just complicate the backends.
Return to the
Search the comp.compilers archives again.