Re: Which GCC in CURRENT? [Was: Re: Wine update]

[David O'Brien]

On Mon, Oct 16, 2000 at 01:21:33PM +0200, Gerald Pfeifer wrote:
> On Mon, 16 Oct 2000, Szilveszter Adam wrote:
> > Also, since 2.96 has not even been released yet, I assume the
> > maintainer (bruce, AFAIK) just makes sure that it builds and compiles
> > stuff OK and so by the time 5.0 will be released and hopefully 2.96
> > too, we just have to push the button and it will be there.
> 
> I can assert, with utmost authority ;-), that GCC 2.96 will never be
> released by the GCC team.

Correct, and FreeBSD 5.0 will ship with 5.0+ release.
The import and use of GCC 2.96(7) in FreeBSD-CURRENT is to support
development of the IA-64, x86-64, and PPC ports.  Since FreeBSD-CURRENT
is not a release and is a tool to use in getting to 5.0, we didn't mind
importing a non-released version of GCC.  Note that FreeBSD's warning of
don't expect stability in -CURRENT will also be very true of the this
compiler.
 
-- 
-- David  ([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc and FreeBSD [was: Re: Which GCC in CURRENT? [Was: Re: Wine update]]

[David O'Brien]

On Tue, Oct 17, 2000 at 04:40:53PM -0400, Marcel Moolenaar wrote:
> > Should any of you have some time to spend, those two PRs I mentioned above
> > are really critical.  

I have issues with one of them -- IMHO FSF/GCC should not assume the
existence of crt{i,n}.o since they supply their own crt{begin,end}.o
(thru crtstuff.c).  There is obivious assumpitons by crtstuff.c on what
crt{i,n}.o supplies, and thus seems logical GCC come with its own
crt{i,n}.s.  This is not to say I am unbending on this (and it also
carries over into JDP's teritory), but I do want to rasie this issue on
the [EMAIL PROTECTED] (after BSDcon) mailing list to see what they say.  

> David: Can you take a look at it, or shall I try to free some time for
> this. It sounds important enough from what I understand from Gerald.

I am tied up at BSDcon for the week.  So I'll reply to this thread better
later.
 
-- 
-- David  ([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc and FreeBSD [was: Re: Which GCC in CURRENT? [Was: Re: Wine update]]

[Marcel Moolenaar]

Gerald Pfeifer wrote:
> 
> Upgrades are not painless at all on FreeBSD, because of some additional
> hacks you/we are using. See the following two PRs for examples that cost
> me quite some time each (and are still open):
> 
>   http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20966
>   http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21983
> 
> If the first PR is not resolved in time for the GCC 3.0 release process
> (which is not that far ahead), FreeBSD might even be dropped from the list
> of secondary evaluation platforms for GCC 3.0. :-(

This worries me. We should not alienate ourself from the development of
"our" toolchain. Ideally, we should have no FreeBSD patches of our own.

> In any case, the bug does prevent regular GCC developers and testers from
> using FreeBSD -- not a good thing, either! :-(

Agreed.

> On the other hand, lately David O'Brien has submitted several patches for
> the FreeBSD ports to GCC, most (all?) of which have been reviewed and
> integrated quickly, so there is a good chance that the difference between
> the FreeBSD version of GCC and FSF GCC will be further reduced. :-)

I don't follow the gcc lists too closely. Time... All I know is that
there was a bit more work to do.

David?

> Should any of you have some time to spend, those two PRs I mentioned above
> are really critical.  

Of course time is always the issue :-)

David: Can you take a look at it, or shall I try to free some time for
this. It sounds important enough from what I understand from Gerald.

-- 
Marcel Moolenaar
  mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
  tel:  (408) 447-4222


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Which GCC in CURRENT? [Was: Re: Wine update]

[Gerald Pfeifer]

On Mon, 16 Oct 2000, Szilveszter Adam wrote:
> Also, since 2.96 has not even been released yet, I assume the
> maintainer (bruce, AFAIK) just makes sure that it builds and compiles
> stuff OK and so by the time 5.0 will be released and hopefully 2.96
> too, we just have to push the button and it will be there.

I can assert, with utmost authority ;-), that GCC 2.96 will never be
released by the GCC team.

See .

> I think this very careful approach on the part of the maintainer(s)
> makes sure that gcc (and binutils and libc) upgrades are so painless
> on FreeBSD, while they can be a significant PITA on Linux because of
> possible incompatibilities.

Upgrades are not painless at all on FreeBSD, because of some additional
hacks you/we are using. See the following two PRs for examples that cost
me quite some time each (and are still open):

  http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20966
  http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21983

If the first PR is not resolved in time for the GCC 3.0 release process
(which is not that far ahead), FreeBSD might even be dropped from the list
of secondary evaluation platforms for GCC 3.0. :-(

In any case, the bug does prevent regular GCC developers and testers from
using FreeBSD -- not a good thing, either! :-(

On the other hand, lately David O'Brien has submitted several patches for
the FreeBSD ports to GCC, most (all?) of which have been reviewed and
integrated quickly, so there is a good chance that the difference between
the FreeBSD version of GCC and FSF GCC will be further reduced. :-)

Should any of you have some time to spend, those two PRs I mentioned above
are really critical.  

Gerald
-- 
Gerald "Jerry" [EMAIL PROTECTED] http://www.dbai.tuwien.ac.at/~pfeifer/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Which GCC in CURRENT? [Was: Re: Wine update]

[Szilveszter Adam]

On Mon, Oct 16, 2000 at 09:49:30AM +0100, Konstantin Chuguev wrote:
> 
> There are two directories in CURRENT's src/contrib: gcc and gcc.295 (the former is
> fresher). In src/gnu/{usr.bin|lib} appropriate Makefile.inc files set .PATH to
> .../.../gcc.295.
> There seems to be no way to switch to another GCC by editing just one line
> somewhere.
> Does anybody knows why there are two GCC in CURRENT?

Because there is a planned upgrade of the gcc to 2.96 sometime in the
future. But the new gcc snapshot contained in that directory (which is also
refreshed sometimes) is not yet ready for prime time. A gcc upgrade is a
very delicate matter and must be planned carefully. Also, since 2.96 has not
even been released yet, I assume the maintainer (bruce, AFAIK) just makes
sure that it builds and compiles stuff OK and so by the time 5.0 will be
released and hopefully 2.96 too, we just have to push the button and it will
be there. 

If you look closely enough, you can also see two parallel gdb trees and at
one time (before the upgrade to the latest release version) there also used
to be two binutils dirs. I think this very careful approach on the part of
the maintainer(s) makes sure that gcc (and binutils and libc) upgrades are
so painless on FreeBSD, while they can be a significant PITA on Linux
because of possible incompatibilities.
 
-- 
Regards:

Szilveszter ADAM
Szeged University
Szeged Hungary


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Which GCC in CURRENT? [Was: Re: Wine update]

[Konstantin Chuguev]

Szilveszter Adam wrote:

> > > Hmmm. It is good that the problem got resolved, but I take both 4.1 and
> > > -CURRENT use the same gcc version... (2.95.2) Or am I missing something?
> >
> > AFAIK, -CURRENT uses a snapshot of GCC 2.96 which may have some bugs.
>
> It reports itself as 2.95.2.
>

There are two directories in CURRENT's src/contrib: gcc and gcc.295 (the former is
fresher). In src/gnu/{usr.bin|lib} appropriate Makefile.inc files set .PATH to
.../.../gcc.295.
There seems to be no way to switch to another GCC by editing just one line
somewhere.
Does anybody knows why there are two GCC in CURRENT?

Regards,
Konstantin.

--
  * *Konstantin Chuguev - Application Engineer
   *  *  Francis House, 112 Hills Road
 *   Cambridge CB2 1PQ, United Kingdom
 D  A  N  T  E   WWW:http://www.dante.net





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message