public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "B. Kosnik" <bkoz@nabi.net>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Atomic operations for PA
Date: Tue, 05 Nov 2002 13:25:00 -0000	[thread overview]
Message-ID: <20021105152322.4b243ba0.bkoz@nabi.net> (raw)
In-Reply-To: <200211052117.gA5LHDUe024207@hiauly1.hia.nrc.ca>


>> I was thinking the same thing, but doesn't it also have to match hppa2.0 and
>> hppa64 as cpu names?  The default would look for three different directories.
>
>Yes.  I did a quick check on hppa-unknown-linux-gnu and unfortunately
>missed this.

Sorry. I guess your patch was more correct as posted. Can you add the
configure.target bits please?

-benjamin

  reply	other threads:[~2002-11-05 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  9:24 John David Anglin
2002-11-05 10:51 ` Benjamin Kosnik
2002-11-05 13:11   ` Phil Edwards
2002-11-05 13:17     ` John David Anglin
2002-11-05 13:25       ` B. Kosnik [this message]
2002-11-05 13:26         ` 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=20021105152322.4b243ba0.bkoz@nabi.net \
    --to=bkoz@nabi.net \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).