From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: gcc-help@gcc.gnu.org
Subject: Re: how to configure for 64bit default on ia64-hp-hpux11*
Date: Mon, 04 Aug 2008 08:31:00 -0000 [thread overview]
Message-ID: <1217838647.7598.20.camel@salomon-22> (raw)
In-Reply-To: <1215523497.21100.30.camel@sapc154.salomon.at>
No response after ~1 month - please tell if wrong list (which one
instead?), thanks!
(more thoughts below)
On Tue, 2008-07-08 at 15:24 +0200, Michael Haubenwallner wrote:
> Hi,
>
> when building for ia64-hp-hpux11*, the default output type is 32bit.
>
> While this is a multilib-compiler by default, I'd like to
> --disable-multilib, and use different target triplets instead of
> compiler flags, very similar to these ones:
>
> 32bit 64bit
> i?86-pc-linux-gnu x86_64-pc-linux-gnu
> i386-sun-solaris2* x86_64-sun-solaris2*
> sparc-sun-solaris2* sparcv9-sun-solaris2*
> hppa2.0*-hp-hpux11* hppa64-hp-hpux11*
> powerpc-ibm-aix5* powerpc64-ibm-aix5*
> ppc-*-linux-gnu ppc64-*-linux-gnu
> <none> ia64-*-linux-gnu
>
> Now, what could be the 64bit target triplet for ia64-hpux ?
>
> 32bit 64bit
> ia64-hp-hpux11* ia64_64-hp-hpux11*
>
> Or should 'ia64-hp-hpux11*' be changed to default to 64bit, and
> introduce some new 'ia64_32-hp-hpux11*' instead ?
>
> 32bit 64bit
> ia64_32-hp-hpux11* ia64-hp-hpux11*
What about these names, inspired by hppa2.0n/hppa2.0w:
ia64-hp-hpux11*: default 32bit, keep as-is
ia64n-hp-hpux11*: default 32bit, eventually new for
completeness
ia64w-hp-hpux11*: default 64bit, new
Thoughts?
Thanks!
/haubi/
next prev parent reply other threads:[~2008-08-04 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 19:21 Michael Haubenwallner
2008-08-04 8:31 ` Michael Haubenwallner [this message]
2008-08-05 14:31 ` Ian Lance Taylor
2008-08-05 20:08 ` Steve Ellcey
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=1217838647.7598.20.camel@salomon-22 \
--to=michael.haubenwallner@salomon.at \
--cc=gcc-help@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).