Re: solaris build problem with Sun compilers
- From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- To: stange(at)rentec(dot)com
- Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-ports(at)postgresql(dot)org
- Subject: Re: solaris build problem with Sun compilers
- Date: Thu, 18 May 2006 12:02:55 -0400 (EDT)
- Message-id: <200605181602.k4IG2tL08931@candle.pha.pa.us> <text/plain>
Alan Stange wrote:
> > Uh, are you saying our Solaris Sparc "cas" ASM is only going to work for
> > Solaris 11 tools? That doesn't sound good. We must have people using
> > earlier Solaris tools.
>
> No, I'm not saying that at all.
>
> I think I'm saying that cas is OK for any reasonable Solaris+Sparc+Sun
> compiler combination. It'll fail on any SuperSparc based hardware and
> older compilers (more than ~5 years), but that's too bad.
Well, when you look at the cost/benefit of using cas vs. ldstub, it
seems logical to keep ldstub for those older platforms.
> I'm also saying that cas in not OK for any gcc+binutils combination. As
> far as I can tell, gcc is still building code for the v7 platform by
> default. It's possible to override this, but I don't think it's
> something you can test for in the preprocessor.
OK, I added a comment that gcc generates sparcv7 binaries.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Home |
Main Index |
Thread Index