On Mon, Aug 21, 2017 at 10:02:44AM +, Christos Zoulas wrote:
> In article <20170820110132.ga5...@britannica.bec.de>,
> Joerg Sonnenberger wrote:
> >On Sun, Aug 20, 2017 at 04:25:47AM -0400, Christos Zoulas wrote:
> >> Module Name: src
> >> Committed By: christos
> >>
On Sun, Aug 20, 2017 at 04:25:47AM -0400, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Sun Aug 20 08:25:47 UTC 2017
>
> Modified Files:
> src/tests/lib/libm: t_fe_round.c
>
> Log Message:
> fix build (missing nexttoward on mips64 and aarch64)
Please
> Date: Wed, 26 Jul 2017 22:02:09 +0300
> From: Valery Ushakov
>
> Also, portmasters could have been asked in advance, at least pro
> forma. If I'm given a heads up and a summary of what needs to be
> done, I can usually schedule it within a few days. When I see a
> commit
On Wed, Jul 26, 2017 at 06:28:16AM +0700, Robert Elz wrote:
> Date:Tue, 25 Jul 2017 22:43:18 +
> From:co...@sdf.org
> Message-ID: <20170725224318.ga3...@sdf.org>
>
> | It's a minor inconvenience to fix a critical bug.
>
> Breaking builds is not a minor
On Wed, Jul 26, 2017 at 03:24:16 +, Taylor R Campbell wrote:
> > Date: Wed, 26 Jul 2017 00:31:48 +0300
> > From: Valery Ushakov
> >
> > On Tue, Jul 25, 2017 at 21:29:33 +, co...@sdf.org wrote:
> > > On Tue, Jul 25, 2017 at 09:26:56PM +, Valeriy E. Ushakov wrote:
Date:Wed, 26 Jul 2017 00:17:49 +
From:co...@sdf.org
Message-ID: <20170726001748.gd3...@sdf.org>
| And it adds an actual test for functionality, to be sure we weren't
| wrong in adding the function for that arch.
That's useful, but you can get that if you
There is no other way to find and fix these problems. nobody runs sh3
tests, and non-x86 ports have so many failures that it's going to be
drowned in the noise.
And it adds an actual test for functionality, to be sure we weren't
wrong in adding the function for that arch.
This is causing
On Wed, Jul 26, 2017 at 05:32:42AM +0700, Robert Elz wrote:
> Date:Wed, 26 Jul 2017 00:31:48 +0300
> From:Valery Ushakov
> Message-ID: <20170725213148.ga16...@pony.stderr.spb.ru>
>
> | You can do that in your tree, not in the public repo.
>
>
On Tue, Jul 25, 2017 at 09:26:56PM +, Valeriy E. Ushakov wrote:
> Module Name: src
> Committed By: uwe
> Date: Tue Jul 25 21:26:56 UTC 2017
>
> Modified Files:
> src/tests/lib/libm: t_fe_round.c
>
> Log Message:
> Revert previous as it breaks at least sparc and hpcsh builds.
>
On Mon, Dec 19, 2016 at 05:44:56PM +, co...@sdf.org wrote:
> I suppose the name is dumb, but I only thought about it
> after committing. sorry.
> It should crash with SIGFPE on alpha, which is why I thought
> of exceptions when naming it!
... except it shouldn't do that either now.
I'm gonna
On Mon, Dec 19, 2016 at 05:38:24PM +, Maya Rashish wrote:
> Module Name: src
> Committed By: maya
> Date: Mon Dec 19 17:38:24 UTC 2016
>
> Modified Files:
> src/tests/lib/libm: Makefile
> Added Files:
> src/tests/lib/libm: t_fe_round.c
>
> Log Message:
> add test for
At Sat, 24 Jan 2015 10:35:01 +,
David Laight wrote:
Log Message:
In the exp2_values test case, provide separate expected return values
for the float case, reflecting the actual exp2f() argument value after
rounding to float precision. Fixes PR lib/49256. Thanks to Makoto
On Tue, Oct 07, 2014 at 04:53:44PM +, Andreas Gustafsson wrote:
Module Name: src
Committed By: gson
Date: Tue Oct 7 16:53:44 UTC 2014
Modified Files:
src/tests/lib/libm: t_exp.c
Log Message:
In the exp2_values test case, provide separate expected return values
for
On Sat, Mar 01, 2014 at 09:08:39PM +, David Laight wrote:
Log Message:
Some of the acos() tests seem to fail on some systems.
Sorting out why isn't helped by the tests not reporting the erronous value.
Change the 'boilerplate' pattern used so that all the values are output.
Reduce the
On Thu, May 23, 2013 at 04:45:47PM -0400, Christos Zoulas wrote:
Module Name: src
Committed By: christos
Date: Thu May 23 20:45:47 UTC 2013
Modified Files:
src/tests/lib/libm: t_scalbn.c
Log Message:
vaxinate the new tests.
To generate a diff of this commit:
cvs
On May 24, 8:01am, mar...@homeworld.netbsd.org (Martin Husemann) wrote:
-- Subject: Re: CVS commit: src/tests/lib/libm
| This is wrong - unlike the other tests that use IEEE FP specific things,
| the value tests should work on vax. I'll have a look and fix it properly.
They could once you add
On Fri, May 24, 2013 at 09:08:18AM -0400, Christos Zoulas wrote:
On May 24, 8:01am, mar...@homeworld.netbsd.org (Martin Husemann) wrote:
-- Subject: Re: CVS commit: src/tests/lib/libm
| This is wrong - unlike the other tests that use IEEE FP specific things,
| the value tests should work
On May 24, 2013, at 6:44 AM, Martin Husemann mar...@duskware.de wrote:
On Fri, May 24, 2013 at 09:08:18AM -0400, Christos Zoulas wrote:
On May 24, 8:01am, mar...@homeworld.netbsd.org (Martin Husemann) wrote:
-- Subject: Re: CVS commit: src/tests/lib/libm
| This is wrong - unlike the other
On Thu, Sep 15, 2011 at 11:05:51AM +, Havard Eidnes wrote:
Module Name: src
Committed By: he
Date: Thu Sep 15 11:05:51 UTC 2011
Modified Files:
src/tests/lib/libm: t_tan.c
Log Message:
#ifdef on __vax__ one more place, to avoid reference to tanf() for vax.
I am not
On Fri, Sep 16, 2011 at 09:02:37AM +, Martin Husemann wrote:
I am not sure if this is correct here. While some tests rely on NAN and
similar IEEE 754 specific properties of the underlying floating point
format should not be build (or skipped) on vax, this test case does not
have any reason
On Fri, Sep 16, 2011 at 09:16:23PM +0300, Jukka Ruohonen wrote:
Is there any consistent way to know which functions are available on VAX?
Or even more generally, any consistent way to know which libm(3) functions
are available on which architectures? (That is, there are ugly hacks like
On Fri, Sep 16, 2011 at 08:41:47PM +0200, Martin Husemann wrote:
On Fri, Sep 16, 2011 at 09:16:23PM +0300, Jukka Ruohonen wrote:
Is there any consistent way to know which functions are available on VAX?
Or even more generally, any consistent way to know which libm(3) functions
are
Am 12.09.11 18:28, schrieb Jukka Ruohonen:
Module Name: src
Committed By: jruoho
Date: Mon Sep 12 16:28:37 UTC 2011
Modified Files:
src/tests/lib/libm: t_ldexp.c t_scalbn.c t_tanh.c
Log Message:
Happiness of VAX implies ugliness of the code.
But does it make the VAX
On Tue, Sep 13, 2011 at 08:38:07AM +0200, Marc Balmer wrote:
Am 12.09.11 18:28, schrieb Jukka Ruohonen:
Module Name:src
Committed By: jruoho
Date: Mon Sep 12 16:28:37 UTC 2011
Modified Files:
src/tests/lib/libm: t_ldexp.c t_scalbn.c t_tanh.c
Log
On Tue, Sep 13, 2011 at 06:50:41AM +, Jukka Ruohonen wrote:
Module Name: src
Committed By: jruoho
Date: Tue Sep 13 06:50:41 UTC 2011
Modified Files:
src/tests/lib/libm: t_scalbn.c
Log Message:
Test that scalbn(x) == ldexp(2) whenever FLT_RADIX == 2 (like it should be
On Tue, Sep 13, 2011 at 09:48:37AM +0300, Jukka Ruohonen wrote:
You are right. I didn't bother to do atf_tc_skip() for the special case of
VAX. If any of the VAX people want to run the tests, please feel free to fix.
Unfortunately this would require (definitively non trivial) gcc fixes first.
In article 20110912162837.5501917...@cvs.netbsd.org,
Jukka Ruohonen source-changes-d@NetBSD.org wrote:
-=-=-=-=-=-
Module Name: src
Committed By: jruoho
Date: Mon Sep 12 16:28:37 UTC 2011
Modified Files:
src/tests/lib/libm: t_ldexp.c t_scalbn.c t_tanh.c
Log Message:
Happiness
101 - 127 of 127 matches
Mail list logo