From: David Huggins-Daines <dhd@linuxcare.com>
To: law@cygnus.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] untested but building 64-bit toolchain, issues/questions
Date: 06 Jul 2000 14:05:39 -0400 [thread overview]
Message-ID: <874s63p218.fsf@linuxcare.com> (raw)
In-Reply-To: Jeffrey A Law's message of "Thu, 06 Jul 2000 10:30:43 -0600"
Jeffrey A Law <law@cygnus.com> writes:
> In message <873dlnl3f9.fsf@linuxcare.com>you write:
> > > Yes, but I thought that 'hppa2.0w' means 64 bit by definition, so it
> > > strikes me that the problem is with config.guess returning this.
> >
> > Oh, and one more thing. GCC thinks that hppa2.0w is a 64-bit target.
> Err, no. Go look at the official GCC, GDB, binutils repositories.
>
> hppa2.0w is not considered a 64bit target by any of the tools.
Urgh. Understood. This means that the gcc tree on
puffin.external.hp.com CVS is quite out of date, which is sort of what
I expected. I'm looking at the possibility of merging it now.
On the subject of architecture strings:
I know Matthew Wilcox has been pushing for using 'parisc-*-linux-gnu'
and 'parisc64-*-linux-gnu' as the arch strings for 32 and 64 bit
targets, and standardising on a 'linux' dialect of assembly language
for both (basically 2.0 mnemonics). What would the chances of this
being accepted by the binutils/gcc/autoconf maintainers be? (should I
be asking this on another list? sorry...)
We need to standardise on these things ASAP, since we are starting to
build userspace, and we will be stuck with them very soon.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-07-06 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 22:25 [parisc-linux] untested but building 64-bit toolchain, issues/questions David Huggins-Daines
2000-07-05 22:39 ` Jeffrey A Law
2000-07-06 14:14 ` David Huggins-Daines
2000-07-06 14:49 ` David Huggins-Daines
2000-07-06 16:30 ` Jeffrey A Law
2000-07-06 18:05 ` David Huggins-Daines [this message]
2000-07-06 18:16 ` Jeffrey A Law
2000-07-06 17:01 ` Jeffrey A Law
2000-07-06 19:01 ` Grant Grundler
2000-07-06 19:19 ` 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=874s63p218.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=law@cygnus.com \
--cc=parisc-linux@thepuffingroup.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