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 10:14:28 -0400 [thread overview]
Message-ID: <87puorl517.fsf@linuxcare.com> (raw)
In-Reply-To: Jeffrey A Law's message of "Wed, 05 Jul 2000 16:39:42 -0600"
Jeffrey A Law <law@cygnus.com> writes:
> 64bit is hppa64-*-*.
>
> We do _not_ want to ever default the tools to 64bit due to the significant
> code generation penalties that involves.
>
> Thus we can not key 64bit generation on the strings returned by config.guess.
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.
> This was discussed on the gcc, gdb, binutils, and autoconf development
> lists.
Can you provide a subject: line to search on or a URL? I can't find
any definitive statements on the semantics of config.guess nor the
proper configuration for 64-bit PA-RISC in the archives.
> I'm not aware of a technical reason why this will not work in the assembler;
> there are *major* problems trying to make this work with the compiler. Feel
Yes, I'm aware of that :) I was hoping to follow the Sparc model where
the compiler is configured to pass the appropriate flags to the
assembler.
> free to try and merge them.
It turns out this isn't a big priority at the moment since we'd prefer
not to break the existing HP/UX support, but if it turns out to be
easy I might.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-07-06 14:14 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 [this message]
2000-07-06 14:49 ` David Huggins-Daines
2000-07-06 16:30 ` Jeffrey A Law
2000-07-06 18:05 ` David Huggins-Daines
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=87puorl517.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