public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [COMMITTED] hppa: Update libm-test-ulps.
Date: Wed, 15 May 2013 21:16:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1305152115140.21321@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5193FA4F.30401@redhat.com>

On Wed, 15 May 2013, Carlos O'Donell wrote:

> I've never regenerated from scratch. We have not recommended that in
> Regeneration or the release process. I always regenerate incrementally
> from the existing file. Though I see your point that we should probably
> make this mandatory.

It's commonly been done for non-x86 architectures, to update the file for 
ulps reductions and tests that have changed name; I try to do it for ARM, 
MIPS and powerpc-nofpu each freeze.  (For x86 the dependency on x87 
implementation and compiler excess precisions makes it riskier, but I 
still think we should do it sometimes.)

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2013-05-15 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 16:29 Carlos O'Donell
2013-05-15 20:22 ` Joseph S. Myers
2013-05-15 21:00   ` Joseph S. Myers
2013-05-15 21:12     ` Carlos O'Donell
2013-05-15 21:16       ` Joseph S. Myers [this message]
2013-05-15 21:08   ` [COMMITTED] hppa: Cleanup libm-test-ulps Carlos O'Donell
2013-07-24  3:34 [COMMITTED] hppa: Update libm-test-ulps Carlos O'Donell

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=Pine.LNX.4.64.1305152115140.21321@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=libc-ports@sourceware.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).