This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: hpux: PA-RISC?? which version?
- To: binutils at sourceware dot cygnus dot com
- Subject: Re: hpux: PA-RISC?? which version?
- From: Robert A Nesius <rnesius at ichips dot intel dot com>
- Date: Tue, 10 Oct 2000 11:32:41 -0700 (PDT)
On Tue, 10 Oct 2000, Jeffrey A Law wrote:
>
> In message <39E31E5D.45DE0830@lufmech.rwth-aachen.de>you write:
> > Hi!
> >
> > Can someone explain, why binutils configured for
> > hppa2.0w-hp-hpux11.00 are PA-RISC1.1 executables?
>
> Because we never under any circumstances want the tools to default to
> creating PA64 binaries.
>
>
> > I had the impression hp cc normally creates PA-RISC2.0
> > executables per default.
>
> HP's compilers create executables specific to the particular PA chip in
> your system. Ie, if you've got a PA1.0 box, you get PA1.0 binaries, if
> you have a PA1.1 box, you get PA1.1 binaries, if you have a PA2.0 box,
> you get PA2.0 binaries. If you ask nicely, you can get PA64 binaries.
>
> If you want PA2.0 binaries from GCC use -mpa-risc-2-0
>
It seems to me we're confusing 64bit vs. 32 bit and PA1.x vs. PA2.x.
PA2.x supports 32-bit binaries with PA2.0 opcodes.
/opt/ansic/bin/cc generates 32bit PA2.0 binaries with +DA2.0,
and 64bit PA2.0 binaries with +DA2.0W.
From the text above, it looks like gcc only does 64-bit on HPPA 2.0?
-Rob
--
#include <sig.h>
------------------------------------------------------------------
Robert Nesius rnesius@ichips.intel.com 503.712.2181
DPG Engineering Computing