You managed to get a working 64bit kernel out of gcc 3.2.x? Last I heard that someone tried this, they failed quite miserably. what did you do to successfully build a 64-bit gcc3 capable of building 64bit kernels?

I will make a better docs later, anyway I will have to do this over on other machines as well. This is (approx.) what I did

- get gentoo on sparc64 as usual
- put everything below in /opt/sparc64
- build binutils with 64 bit support
- compile gcc 3 as crosscompiler
- rebuild gcc 3 as native using the gcc above
- build glibc with 64bit support (this is no working right now for me)

here is a real dirty but very quick mindless hack, don't shoot me
- open 2 xterm/kshell/vt/whatever
- in one do the usual make menuconfig;make dep;make clean stuff
- in the 2nd export PATH=/opt/sparc64/bin:$PATH
so the new gcc will be used
make vmlinux, this will fail on 2 points with sth like GLIBC2.2 unresolved symbol,
Appently kernel builds some userlands stuff to get consolehash/pci stufffs
Don't worry, switch to the 1st vc type make vmlinux and hit the ctrl-c real fast after it compile the userland thinggy
make modules, make modules_install

Sorry for the explaination, but I am @home with no sparc and this week I think I will be hunting down the bug, when I finish it I will publish my finding + command log

Well things were better when I left the office, but my sunhme module was not loading (missing symbols), apart from that everything seemed normal

the good news is that the sun is still running after several crash test (with egcs compiled kernel it didn't survie even one test run), the bad news, I still don't know if this is really compiler related, are there any developers of sparc reading this thread who can give ant comments? Please I need to know if egcs is the cause of the crash, the suns are in a production enviroment and I really want them to run Linux instead of solaris,

I could give your kernel a shot. See how it boots. No idea if it'd have the same config I have in mine (Sun Blade 100). As for an account, my sun system sits behind my x86 system, so the only way to access it from the outside is to have an account on both, which I tend not to give out alot... 64-Bit Glibc sounds a whole different can of worms. I've already learned mips64 glibc is a pain in the neck and thensome, sparc64 glibc doesn't sound much different, minus the multiple ABIs.

With regards to mips64 stuff, it seems mainly to be an issue surrounding the several ABIs (o32, n32, n64). Ulrich, guy who runs glibc, seems hellbent on not allowing multiple ABIs for one arch, my guess is to avoid as much confusion as possible. I'm not too knowledgable on why this is, more information can usually be gleaned from reading the libc mailing list on the matter. Suffice to say, mips64 is probably a ways off.