public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: thomas@codesourcery.com
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: [attention machine maintainers] [PATCH] <math.h> issignaling
Date: Mon, 25 Mar 2013 18:39:00 -0000	[thread overview]
Message-ID: <20130325.143945.953041692558823661.davem@davemloft.net> (raw)
In-Reply-To: <87mwts2cpc.fsf@schwinge.name>

From: Thomas Schwinge <thomas@codesourcery.com>
Date: Mon, 25 Mar 2013 07:52:31 +0100

> On Sun, 24 Mar 2013 17:30:33 -0400, David Miller <davem@davemloft.net> wrote:
>> From: Thomas Schwinge <thomas@codesourcery.com>
>> Date: Fri, 22 Mar 2013 12:17:19 +0100
>> 
>> > I have now pushed a new version of this patch in the
>> > tschwinge/issignaling branch.  Would machine maintainers please test
>> > this branch/patch and report back?
>> 
>> It doesn't even build on sparc because the code block that is
>> CPP enabled in the ldbl-128 version of issignaling() has
>> an #error in it.
> 
> Yes, because that code has not yet been tested, as the #error says --
> sorry for not telling that in advance.  Do you want me to publish a new
> branch and/or patch with that line removed?

With the #error line removed, sparc builds cleanly and there are no
testsuite regressions.

I tested with 32-bit sparc V9, which is generally very harmonious with
64-bit sparc.  But I'll kick off a 64-bit build as well and let you
know if anything turns up.

  reply	other threads:[~2013-03-25 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8762148l9v.fsf@schwinge.name>
2013-03-22 11:18 ` Thomas Schwinge
2013-03-24 21:30   ` David Miller
2013-03-25  6:52     ` Thomas Schwinge
2013-03-25 18:39       ` David Miller [this message]
2013-03-25 15:54   ` Carlos O'Donell
2013-03-26 17:34   ` Joseph S. Myers
2013-03-28 12:16     ` Thomas Schwinge
2013-04-03 12:17       ` Thomas Schwinge

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=20130325.143945.953041692558823661.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=thomas@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).