Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pete Carr <pecarr@linux.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Bug 23438. Support for 128-bit long double types on PowerPC  64]
Date: Wed, 12 Jul 2006 03:51:00 -0000	[thread overview]
Message-ID: <20060712035104.GB7182@nevyn.them.org> (raw)
In-Reply-To: <44B42374.1000109@linux.ibm.com>

Just one trivial piece of feedback; Mark covered all the big issues.

On Tue, Jul 11, 2006 at 03:17:24PM -0700, Pete Carr wrote:
> +powerpc64-*-*-*)

The canonical form is "powerpc64-*-*", with only two stars.  The last
star matches things like "linux-gnu", but also other things like
"netbsd" which don't have an extra dash.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-07-12  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 22:17 Pete Carr
2006-07-11 22:59 ` Mark Kettenis
2006-07-12  3:51 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-26 16:44 Pete Carr

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=20060712035104.GB7182@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pecarr@linux.ibm.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