public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: joseph@codesourcery.com (Joseph S. Myers)
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] Enable TImode tests (Re: Enable TImode vs. float conversion routines in libgcc)
Date: Fri, 17 Dec 2010 19:31:00 -0000	[thread overview]
Message-ID: <201012171851.oBHIpaLR026692@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1012171551340.5744@digraph.polyomino.org.uk> from "Joseph S. Myers" at Dec 17, 2010 03:52:03 PM

Joseph S. Myers wrote:
> On Fri, 17 Dec 2010, Ulrich Weigand wrote:
> 
> > The patch below adds __SPU__ as platform supporting TImode in all
> > testcases I could find that use the gcc.dg/titype-1.c pattern.
> > 
> > Note that only some of them mention _WIN64 -- I'm not sure if this
> > was deliberate or an oversight (and I don't have access to a Win64
> > system at the moment), so I left this situation as is.
> > 
> > Does this look good to you, or do you see anything I overlooked?
> 
> As far as I can see this is fine, and I doubt the _WIN64 differences are 
> deliberate.

OK, thanks again!  I've now checked in the patch.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com

  reply	other threads:[~2010-12-17 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 19:46 [spu, commit] Enable TImode vs. float conversion routines in libgcc Ulrich Weigand
2010-12-16 20:07 ` Joseph S. Myers
2010-12-17 15:31   ` [patch] Enable TImode tests (Re: Enable TImode vs. float conversion routines in libgcc) Ulrich Weigand
2010-12-17 16:26     ` Joseph S. Myers
2010-12-17 19:31       ` Ulrich Weigand [this message]
2010-12-17 15:18 ` [spu, commit] Fix TImode->SFmode conversions " Ulrich Weigand

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=201012171851.oBHIpaLR026692@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).