All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Alexander Viro <viro@math.psu.edu>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: 25 May 2001 09:02:01 +0200	[thread overview]
Message-ID: <u8r8xd3o9i.fsf@gromit.moeb> (raw)
In-Reply-To: <20010524234240.G23155@vitelus.com>
In-Reply-To: <20010524234240.G23155@vitelus.com> (Aaron Lehmann's message of "Thu, 24 May 2001 23:42:40 -0700")

Aaron Lehmann <aaronl@vitelus.com> writes:

> On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> > Should we file bug reports against glibc?
> 
> invsqrtpi=  5.64189583547756279280e-01
> Inverted square root of pi. Want to file a bug on Pi?
> 
> tpi      =  6.36619772367581382433e-01,
> R0/S0 on [0, 2.00]
> 
> I'm not sure what R and S are, but the glibc developers probably are.

We have comments in the code that state how j0 is build, and R0/S0
come from some expansion:
 * Bessel function of the first and second kinds of order zero.
 * Method -- j0(x):
 *	1. For tiny x, we use j0(x) = 1 - x^2/4 + x^4/64 - ...
 *	2. Reduce x to |x| since j0(x)=j0(-x),  and
 *	   for x in (0,2)
 *		j0(x) = 1-z/4+ z^2*R0/S0,  where z = x*x;
 *	   (precision:  |j0-1+z/4-z^2R0/S0 |<2**-63.67 )

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  parent reply	other threads:[~2001-05-25  7:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200105250559.f4P5x80365151@saturn.cs.uml.edu>
2001-05-25  6:03 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Aaron Lehmann
2001-05-25  6:34   ` Alexander Viro
2001-05-25  6:42     ` Aaron Lehmann
2001-05-25  6:58       ` Alexander Viro
2001-05-25  7:02       ` Andreas Jaeger [this message]
2001-05-25  7:05         ` Alexander Viro
2001-05-25 10:56     ` Erik Mouw
2001-05-25 11:56       ` Alexander Viro
2001-05-25 12:44     ` Pavel Machek
2001-05-29  1:38 Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26 11:09 Adam J. Richter
2001-05-26  3:10 Adam J. Richter
2001-05-26 11:00 ` James Sutherland
2001-05-29  0:03   ` Jamie Lokier
2001-05-29  0:24     ` Alan Cox
2001-05-29  0:55       ` Jamie Lokier
2001-05-26  2:34 Adam J. Richter
2001-05-26  2:38 ` Larry McVoy
2001-05-26  4:52 ` Jeff V. Merkey
2001-05-25 17:02 Adam J. Richter
2001-05-25 17:23 ` Jacob Luna Lundberg
2001-05-25 18:30 ` Larry McVoy
2001-05-25 22:30   ` Aaron Lehmann
2001-05-26  1:43     ` Larry McVoy
2001-05-25 19:14 ` Doug Ledford
2001-05-25 10:36 Adam J. Richter
2001-05-25  9:34 Adam J. Richter
2001-05-25 16:06 ` Doug Ledford
     [not found] <mailman.990765360.7016.linux-kernel2news@redhat.com>
2001-05-25  6:02 ` Pete Zaitcev
     [not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25  5:57 ` Aaron Lehmann
2001-05-25  6:26   ` Matthew Jacob
2001-05-25  6:31     ` Aaron Lehmann
2001-05-25  4:34 Aaron Lehmann
2001-05-25  5:07 ` Greg KH
2001-05-25 10:00 ` John Cavan
2001-05-25 11:10   ` Alan Cox
2001-05-25 16:17 ` Alan Cox

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=u8r8xd3o9i.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=aaronl@vitelus.com \
    --cc=acahalan@cs.uml.edu \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.