From: Joseph Myers <joseph@codesourcery.com>
To: GT <tnggil@protonmail.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] PPC64: Addition of SIMD cosf function for POWER8.
Date: Tue, 5 Mar 2019 21:59:47 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1903052157150.18440@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1v44fML8uPvIYTJ46wzoIRRXfK_ZbimL1qXr4pthJenC2ZfEm8QtPXwzAgE6bIemC5MygZZpPkkRC4_MDyvjGql8yrWg55YGXVjPMIR153U=@protonmail.com>
On Sun, 3 Mar 2019, GT wrote:
> A namespace correction for constants in the double-precision
> implementation is here. cos/cosf are together in BZ #24205, so it
> should be okay that changes for both are in the same patch.
If you find anything in an earlier patch in the series that should be
corrected, you should repost the earlier patch with the correction
included, rather than having a patch series where a later patch fixes a
bug in an earlier version.
> As an aside, while examining the x86_64 implementation, I found
> about two-dozen files missing the FSF copyright header. They are
> all the single-line files shown when you run this command:
See the Information for Maintainers of GNU Software: it's only files with
more than ten lines that necessarily need copyright and license notices; a
single-line file is not significant for copyright purposes.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-03-05 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 10:07 [PATCH] PPC64: Addition of SIMD cosf function for POWER8 GT
2019-03-05 21:59 ` Joseph Myers [this message]
2019-03-06 21:02 ` Joseph Myers
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1903052157150.18440@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=tnggil@protonmail.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).