From: Jeffrey A Law <law@cygnus.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc@gcc.gnu.org, gdb@sourceware.cygnus.com,
binutils@sourceware.cygnus.com, autoconf@sourceware.cygnus.com
Subject: Re: PA64 configure issues
Date: Tue, 25 Apr 2000 12:20:00 -0000 [thread overview]
Message-ID: <11722.956686264@upchuck> (raw)
In-Reply-To: <200004251814.OAA28140@mal-ach.watson.ibm.com>
In message < 200004251814.OAA28140@mal-ach.watson.ibm.com >you write:
> Geoff gave the background on 64-bit AIX support which can support
> both modes with a single toolchain, defaulting to 32-bit mode. This also
> happens to be the way that the AIX product compilers operate, so the two
> are consistent.
Good.
> The above line in your original message jumps out at me. Are you
> saying that you must build an entirely separate compiler for PA64? Also,
> you did not mention how HP's commercial toolchain operates/defaults.
Yes, we have to build a separate toolchain. Among other things PA32 and PA64
use completely different object file formats (SOM & ELF respectively) one
supports gnu-ld (PA64) the other will never support gnu-ld (PA32). There's
other issues, but those are the two biggest.
HP's tools work by having a front-end which invisibly fires up the appropriate
32bit or 64bit tool based on runtime flags.
> I would agree that defaulting to 32-bit mode, even on 64-bit
> hardware, is the best choice when the hardware can support both modes.
OK.
> If
> the user needs to configure and build a completely separate toolchain for
> 64-bit mode, that is much more cumbersome than the AIX toolchain.
Yup. And that's the root of the problem I'm trying to resolve.
> If HP's
> toolchain defaults differently, I think that you need to consider
> user-interface compatibility as well.
I don't think we're going to have that kind of compatibility. At least not
at this stage.
jeff
next parent reply other threads:[~2000-04-25 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200004251814.OAA28140@mal-ach.watson.ibm.com>
2000-04-25 12:20 ` Jeffrey A Law [this message]
[not found] <11276.956679822@upchuck>
2000-04-25 13:52 ` Alexandre Oliva
[not found] <20378.956845658@upchuck>
2000-04-27 11:00 ` Alexandre Oliva
2000-04-27 11:09 ` Jeffrey A Law
2000-04-27 11:37 ` Alexandre Oliva
2000-04-27 13:26 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11722.956686264@upchuck \
--to=law@cygnus.com \
--cc=autoconf@sourceware.cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox