Rayson Ho wrote: > On Tue, Jan 27, 2009 at 4:43 PM, "C. Bergstr?m" > <cbergstrom at netsyncro.com> wrote: > >> Current patches and status are here >> http://bugs.osunix.org/browse/OSUNIX-44 >> > > Chris, that's really good progress... And BTW, I took a very quick > look at the open64-solaris6.diff patch -- is it all that's needed to > get the open64 compiler binary? > Hi Rayson,
h3sp4wn has been the one working on this, but I can give you access to a cloned working environment any time someone wants to check it out. After the port is /done/ we'll package it and start using it as our default c++ compiler and start testing the c code generation. > > >> It's not done and I think there's a few sticky points left.. For example the >> building of gnu ld.. and also the gnu as + gcc being needed for 64bit code.. >> > > Not sure when exactly GNU as & ld are needed... If you can get Open64 > to translate C code into assembly language code, then the port should > be "done" -- as the assemble step and the link step are almost > idential to those of gcc on Solaris. > > And gas & ld should "just" work on Solaris, since the AMD64 ELF ABI is > same on Solaris AMD64 and Linux AMD64 (and IIRC, FreeBSD ELF on > AMD64). In fact, a few months ago I did the experiment of generating > object files on Linux and linking them on Solaris. > > I googled for gcc solaris m64 amd64, there are some minor gcc build > problems on Solaris, but none of them fatal. > > Even more interesting is that someone tried to bootstrap gcc to get a > 64-bit gcc binary: > > http://gcc.gnu.org/ml/gcc-help/2008-12/msg00196.html > I'd have to confirm, but he's been building gcc all sorts of ways and would know best.. > > >> Anyway.. if anyone wants to take a quick look at the patch, give a quick tip >> or helping hand we'd most appreciate it. >> > > While I have experience with porting compilers, I have never ported > linkers and assemblers. However, I am happy to look at it if we can > break down the Open64 Solaris port into manageable work items :-P > I'll have to toss this in the build queue.. upload a new log and check for errors.. From there we'll have an absolute list of errors we can break down. ./C
