From: Richard Henderson <rth@redhat.com>
To: Jeffrey A Law <law@redhat.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
alan@linuxcare.com.au, rhirst@linuxcare.com,
parisc-linux@thepuffingroup.com, gcc-bugs@gcc.gnu.org
Subject: Re: pa reload problem
Date: Fri, 8 Dec 2000 22:55:52 -0800 [thread overview]
Message-ID: <20001208225552.A4476@redhat.com> (raw)
In-Reply-To: <23471.976334727@upchuck>; from Jeffrey A Law on Fri, Dec 08, 2000 at 09:05:27PM -0700
On Fri, Dec 08, 2000 at 09:05:27PM -0700, Jeffrey A Law wrote:
> Unfortunately, I can't actually test it yet to see what problems removing
> that old hack will expose...
Heh. Perhaps you could forward it to the hppa-linux folk and
see what happens there. Mayhap their linker is differently
crash-prone.
r~
next prev parent reply other threads:[~2000-12-09 6:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 0:23 [parisc-linux] pa reload problem Alan Modra
2000-12-01 6:12 ` John David Anglin
2000-12-01 7:00 ` Alan Modra
2000-12-02 7:33 ` John David Anglin
2000-12-02 7:48 ` John David Anglin
2000-12-02 23:28 ` John David Anglin
2000-12-05 19:42 ` John David Anglin
2000-12-06 20:41 ` John David Anglin
2000-12-07 0:16 ` Richard Henderson
2000-12-07 0:57 ` John David Anglin
2000-12-07 1:18 ` John David Anglin
2000-12-08 22:05 ` John David Anglin
2000-12-08 23:45 ` Richard Henderson
2000-12-09 1:07 ` John David Anglin
2000-12-09 1:39 ` Richard Henderson
2000-12-09 3:12 ` John David Anglin
2000-12-09 4:05 ` Jeffrey A Law
2000-12-09 6:55 ` Richard Henderson [this message]
2000-12-11 17:29 ` Jeffrey A Law
2000-12-11 18:48 ` John David Anglin
2000-12-11 23:51 ` Alan Modra
2000-12-09 7:52 ` Alan Modra
2000-12-09 7:55 ` Richard Henderson
2000-12-09 8:35 ` Alan Modra
2000-12-09 13:57 ` Alan Modra
2000-12-09 18:56 ` Richard Henderson
2000-12-09 23:35 ` Alan Modra
2000-12-22 17:21 ` John David Anglin
2000-12-30 19:05 ` John David Anglin
2001-01-01 23:24 ` Jeffrey A Law
2000-12-11 21:27 ` Michael Meissner
2000-12-02 12:35 ` Alan Modra
2000-12-02 19:43 ` Richard Henderson
2000-12-02 23:01 ` John David Anglin
2000-12-03 1:50 ` Richard Henderson
2000-12-03 3:30 ` Alan Modra
2000-12-02 23:08 ` John David Anglin
2000-12-04 1:41 ` Alan Modra
2000-12-04 18:41 ` Richard Hirst
[not found] <20001201202613.E7166@linuxcare.com>
2000-12-02 7:15 ` Alan Modra
2000-12-04 18:40 ` Richard Hirst
2000-12-04 22:55 ` Alan Modra
2000-12-04 23:08 ` John David Anglin
2000-12-04 23:59 ` Alan Modra
2000-12-05 0:50 ` John David Anglin
2000-12-05 5:33 ` Alan Modra
[not found] <no.id>
2000-12-14 0:48 ` John David Anglin
2000-12-14 3:43 ` Jeffrey A Law
2000-12-14 16:40 ` John David Anglin
2000-12-27 20:08 ` Jeffrey A Law
2000-12-28 5:18 ` John David Anglin
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=20001208225552.A4476@redhat.com \
--to=rth@redhat.com \
--cc=alan@linuxcare.com.au \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-bugs@gcc.gnu.org \
--cc=law@redhat.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=rhirst@linuxcare.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