> look at gcc's behaviour. This has left me somewhat confused. I
> appear to have two complete copies of gcc - one in src/contrib/gcc and
> another in src/contrib/egcs/gcc.
WIP. src/contrib/egcs is the current home. It is moving to
src/contrib/{gcc,libio,libstdc++,etc.}. After the move, it w
According to Peter Jeremy:
> That's the way I remembered things. What threw me is that I currently
> have two _different_ gcc directories, both claiming to be EGCS 1.1.2,
> and both being updated.
The main reason is that we don't lose history with the directory change. At
first we had contrib/gc
: > David O'Brien is working on this now but I think he's
: >suffering from gcc-induced insanity. :-)
Actually, I'd bet more on amd induced insanity rather than gcc. There
have been too many problems with amd of late...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
Peter Wemm <[EMAIL PROTECTED]> wrote:
>Peter Jeremy wrote:
>> I appear to have two complete copies of gcc - one in src/contrib/gcc
>> and another in src/contrib/egcs/gcc.
>src/contrib/gcc is where gcc used to live. Then along came egcs with a
>cygnus-style tree that ended up in src/contrib/egcs
Peter Jeremy wrote:
> The recent thread about the GCC optimiser prompted me to go and have a
> look at gcc's behaviour. This has left me somewhat confused. I
> appear to have two complete copies of gcc - one in src/contrib/gcc and
> another in src/contrib/egcs/gcc. Both of them have README file
The recent thread about the GCC optimiser prompted me to go and have a
look at gcc's behaviour. This has left me somewhat confused. I
appear to have two complete copies of gcc - one in src/contrib/gcc and
another in src/contrib/egcs/gcc. Both of them have README files
stating that they are EGCS
