GCC 3.3 Update for Mac OS X Available
snowtigger writes "The August 2003 GCC updater includes the new GCC 3.3 compiler in addition to other updates that will allow development of G5 optimized code with the December 2002 Mac OS X Developer Tools. This update is available to all ADC members from the Download Software area of the ADC web site (free registration required). It will be interesting to see what Steve Jobs will present in Paris tomorrow; is XCode ready?"
The keynote starts at 1 AM Pacific time...
i'm the jedidiahmarkfoster your parents warned you about
The GCC update has been out for a while, but it looks like last week Apple updated CHUD (the Computer Hardware Understanding Development toolkit) to version 3.0.
It lets you tweak configuration registers in almost all parts of the system, gather and graph lots of profile information (instruction mix, cache stalls, etc...) from programs, and lots of other cool things.
The ABI is Mach-O or CFM. They both work on OS X. GCC uses it, Codewarrior uses it, the IBM XL compilers use it. Codewarrior also beats gcc in speed & quality of code like an abusive sibling*. Donno about the IBM compilers, but I assume they provide an even more severe beating.
* That was going to be a much more offensive analogy...
Care about electronic freedom? Consider donating to the EFF!
Fink users: see this annoucement from the Fink developers regarding GCC 3.3 . It is probably a good idea to hold off on installing 3.3 until they add support for it.
You won't need gcc, what made you think that ?
From the Fink site:
2003-06-26: Developer Tools Update.
Quick Summary: DO NOT INSTALL THIS UPDATE.
Apple has released a patch to the December 2002 Developer Tools which includes gcc 3.3, their new compiler.
Fink does not yet support compiling with gcc 3.3. In addition, it is important not to "mix and match" between compilers: all C++ code in fink packages needs to be compiled with the same compiler.
For this reason, the Fink team recommends that if you update your Developer Tools with the new patch, you should be careful to run sudo gcc_select 3 prior to any "fink build" or "fink install" commands.
It works as advertised.
It's _very_ fast too.
GCC is for compiling software from raw source code. If you're downloading open source software, you generally need a compiler to install it, because the software frequently isn't distributed in an executable form. Even if an executable form is available, most open source projects don't have the resources to provide version for every esoteric configuration people might be using (like, say, OSX -- most of this stuff is written for Linux after all, so OSX is a bit "exotic" from the average Linux developer's point of view).
If you're not developing software and you don't intend to install open source software from raw source, then you don't need a compiler.
DO NOT LEAVE IT IS NOT REAL
First off, this was about the C++ ABI used by GCC, which indeed changed (again!) between GCC 3.1 and 3.3, meaning that C++ code is incompatbile between those versions.
Next, Mach-O and CFM are binary executable formats, which is a whole other story. Besides, you make it sound as if they were the same, when in fact they are not. They are two very different formats. CFM is the one used traditonally, the only one supported by classic MacOS. Max OS X also supports it, and in fact if you want your Carbon programs to run both on OS 9 and OS X, you have to supply them in CFM. However, GCC is *not* able of outputting CFM. The only C/C++ compiler running on OS X which support this is (AFAIK) MetroWerks CodeWarrior.
Mach-O is the binary format of choice for anything else which only runs on OS X, and it's the only format GCC and the IBM XL compiler support (on OS X, that is).
anyone looking for the IBM XL C and XL C++ compiler beta can look here
i doubt this will remain free. better snag it now!
It's not complete nonsense :-P
:-) bbl.
The ABI that matters is for C on OS X. Carbon uses it. Even Objective-C & Cocoa use it (the calls are mapped to a C call).
As for C++ ABI... I'm asking someone who knows
Care about electronic freedom? Consider donating to the EFF!
The Dec2002gccUpdater.pkg update:
/usr/libexec/gcc/darwin/ppc/3.3/specs
/usr/libexec/gcc/darwin/ppc/3.3/specs
% gcc -v
Reading specs from
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1435)
The NEW August2003gccUpdater.pkg update:
% gcc -v
Reading specs from
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1493)
CFM & Mach-O are the OS 9 & OS X binary executable formats. They can be as different as they want internally, but they're serving the same purpose. I think we're in agreement here.
My point was that the C ABI is standard atop of these, and that that's the ABI that's most important. I'll post when I get the right info on the C++ ABI compatibility...
Care about electronic freedom? Consider donating to the EFF!
O'Reilly's MacDev center
CocoaDev.com
Both have entry-level ProjectBuilder tutorials, including the famous one-line web browser (CocoaDev) and text editor (O'Reilly) tutorials.
Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
Seriously, it's well worth the money to get yourself a processor upgrade card given the machine you've just bought. I'm pretty sure you can upgrade to 800Mhz or 1GHz for a reasonable price. This is what has kept prices for these machines and Cubes so high. It'll more than double your performance considering the added cache, and that'll make a big difference if you're compiling. Also max out your RAM, it's cheap.
Rather than complain about the puck, dual-button+scrollwheel optical USB mice are super-cheap, get one.
Project Builder is already pretty damn sweet, and has been for some time. Try it out now, it'll make the transition to Xcode smoother for you.