Solaris 8 64-bit C compilation fails to add .register declaration

[Vic Abell]

Nicolas,

I've learned that gcc patches from the capable
Casper Dik have been incorporated into the latest
2.96 snapshots.  I downloaded 20000207 and was able
to build a 64-bit-capable Solaris 2.7 gcc with no
special effort -- i.e., no sparcv9 declarations on
the configure step.

The resulting gcc built a working lsof for 64 bit
Solaris 7.

I understand the resulting gcc may have other sparcv9
problems, so don't take this message as an endorsement
of the compiler for general use.

Vic

> -----Original Message-----
> From: Nicolas Williams [ mailto:Nicolas.Williams@wdr.com ]
> Sent: Tuesday, January 11, 2000 11:39 AM
> To: Martin v. Loewis
> Cc: gcc-bugs@gcc.gnu.org; law@cygnus.com; abe@purdue.edu
> Subject: Re: Solaris 8 64-bit C compilation fails to add .register
> declaration
> 
> 
> On Tue, Jan 11, 2000 at 02:07:53AM +0100, Martin v. Loewis wrote:
> > > I believe this non-emission constitutes a bug.
> > 
> > Thanks for your bug report. This is a bug, indeed. It is not the only
> > one.
> > 
> > > I found instructions for building a 64-bit-capable GCC for Solaris 8
> > > on UltraSPARCs
> > 
> > Don't follow such instructions. They mislead you by giving the
> > impression that gcc supports sparcv9 (aka sparc64). It does not. Don't
> > use gcc on that architecture, at least not in 64-bit mode. It is not
> > supported, and has numerous bugs.
> > 
> > Regards,
> > Martin
> > 
> > P.S. If I only could get the FAQ-o-matic to work for me again, so I
> > could add this to the FAQ...
> 
> Thanks for your quick reply.
> 
> Note also that the LSOF FAQ for LSOF 4.47_W provides some instructions
> for building GCC for building 64-bit UltraSPARC binaries.
> 
> Between the changlogs for GCC 2.95.2, the LSOF FAQ and the instructions
> I found on Usenet I came to believe that this was doable.
> 
> I guess the GCC and LSOF FAQs need updating then.
> 
> Thanks,
> 
> Nico
> 
> PS: Note I'm CC'ing this mail to LSOF's maintainer, Vic Abell <abe@purdue.edu>.
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please 
> notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free 
> as information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses.  The sender therefore 
> does not accept liability for any errors or omissions in the contents 
> of this message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 
>