According to Ulf Carlsson ...
>
> > The situation for userland is different and much more complex. GNU libc and
> > other packages do heavily rely on GNU ld's features. Add that GNU ld is
> > evolving. That makes using anything but GNU ld a no go for userspace.
>
> I was talking to Ralf earlier and I mentioned that I thought SGI was going to
> use the MIPS Pro compiler to compile the Linux that will run on the IA-64 SN1
> machines. I really don't know what's happening with the MIPS Pro compiler
> nowadays, I've only heard rumours from here and there. If the MIPS Pro
> compiler is going to be used to compile Linux I assume that the GNU specific
> features required to compile the GNU libc, such as symbol versioning, will be
> added, and we can use the features for MIPS as well as IA-64. Does anyone
> know whether the MIPS Pro compiler for IA-64 will be open sourced or not?
I dont think symbol versioning etc will be added to the MIPS pro tool set.
The version running on babylon.engr has lots of problems and we found it
hard to even build the kernel. Forget MIPSpro for anything in linux.
The way ia64 tools are structured is that most of the pieces are taken
from the cygnus open source gcc. Just the optimization is sgi contribution.
preprocessor, parser+intermediate codegen assembler loader linker for ia64
is gcc based. The MIPSpro type of optimization algorithms have been
re-implemented for ia64. SGI intends to open source ia64 tools but
current are waiting for a nod from Intel.
Srinivasa
>
> Ulf
>
|