Contributed by jose on from the big-changes dept.
Date: Fri, 20 Feb 2004 20:04:19 -0700 (MST) From: Theo de Raadt <deraadt@cvs.openbsd.org> To: source-changes@cvs.openbsd.org Subject: CVS: cvs.openbsd.org: src CVSROOT: /cvs Module name: src Changes by: deraadt@cvs.openbsd.org 2004/02/20 20:04:19 Modified files: share/mk : bsd.own.mk Log message: move sparc64 to gcc3. to move up please install a snapshot (or, install this, build the right gcc, do a make build and pray)
(Comments are closed)
By Peter Hessler () on
PITA. I'm going to upgrade via snapshot next time.
Comments
By Steven () on
By Marc Espie () espie@openbsd.org on mailto:espie@openbsd.org
You tell me.
However, it is much easier now than it was when I did the actual import and relevant bug-fixing...
;-)
By Anonymous Coward () on
By Dheeraj () on
Comments
By Marc Espie () espie@openbsd.org on mailto:espie@openbsd.org
Comments
By van Rijn () on
Is the code not compatible?
That disapoint me couse I think nobody told us exactly why the i386-port will use the old gcc.
Comments
By Marc Espie () espie@openbsd.org on mailto:espie@openbsd.org
sparc64 is a good candidate. The support of
sparc64 in gcc 2.95 is not good at all.
If you follow cvs commits, there has been a hefty number of changes to *remove* sparc64 work-arounds in the ports tree after gcc3 got committed.
On the other hand, i386 is fairly stable with gcc 2.95. gcc 3.3.2 is a lot slower than gcc 2.95. So, the benefits aren't that great.
Going to gcc 3.3.2 can't hurt sparc64 much. It's a win on almost all accounts. And it gives us a chance to see more real-life testing of gcc 3.3.2, before we move other platforms.
Also note that a few applications will need updates AND debug before they run with gcc3.
The whole mozilla family currently doesn't run on OpenBSD i386 when compiled with gcc3.