From: Cary Coutant <cary@cup.hp.com>
To: "Cary Coutant" <cary@cup.hp.com>,
"David Huggins-Daines" <dhd@linuxcare.com>
Cc: <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] PIC code generation in gcc/binutils
Date: Tue, 25 Jul 2000 10:21:45 -0700 [thread overview]
Message-ID: <200007251723.KAA02344@adlmail.cup.hp.com> (raw)
>I realize that the 64-bit runtime
>architecture is weak in the dynamic loading area, ...
By the way, I meant the documentation, not the runtime architecture
itself!
next reply other threads:[~2000-07-25 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 17:21 Cary Coutant [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-25 17:20 [parisc-linux] PIC code generation in gcc/binutils Cary Coutant
2000-07-24 23:58 Cary Coutant
2000-07-25 0:05 ` Ulrich Drepper
2000-07-25 0:23 ` David Huggins-Daines
2000-07-25 1:12 ` Alan Modra
2000-07-25 14:36 ` Matthew Wilcox
2000-07-25 15:16 ` Matthew Wilcox
2000-07-18 17:58 David Huggins-Daines
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=200007251723.KAA02344@adlmail.cup.hp.com \
--to=cary@cup.hp.com \
--cc=dhd@linuxcare.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