> -Original Message-
> From: Andriy Gapon [mailto:a...@freebsd.org]
> Sent: 6. november 2012 19:53
> To: Tom Lislegaard
> Cc: freebsd-stable@FreeBSD.org; freebsd-a...@freebsd.org
> Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource
>
> on 06/11/2012 10:50 Tom Lisleg
on 08/11/2012 11:06 Tom Lislegaard said the following:
>
>> -Original Message-
>> From: Andriy Gapon [mailto:a...@freebsd.org]
>> Sent: 6. november 2012 19:53
>> To: Tom Lislegaard
>> Cc: freebsd-stable@FreeBSD.org; freebsd-a...@freebsd.org
>> Subject: Re: 9-Stable panic: resource_list_unr
I unfortunately confirm this problem.
While not "true and only way", I had impression, that
(at this point) 9-STABLE should be possible to build with
clang at any time.
After all, building with clang started with essentially
still 8 code.
With introduction of:
WITH_CLANG_IS_CC=true
WITHOUT_GC
> -Original Message-
> From: Andriy Gapon [mailto:a...@freebsd.org]
> Sent: 8. november 2012 11:53
> To: Tom Lislegaard
> Cc: freebsd-stable@FreeBSD.org; freebsd-a...@freebsd.org
> Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource
>
> on 08/11/2012 11:06 Tom Lisle
I can confirm something similar.
$ dc
18446744073709551616 18446744073709551616 / ps
dc: big number failure 306b06b: No error: 0
FreeBSD 9.1-PRERELEASE #0 r242513 amd64, clang
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/dc-1-fails-with-big-number-failure-on-2-64-tp5
On 11/08/2012 03:06, Jan Mikkelsen wrote:
Hi,
I am seeing this in dc:
janm@gray: dc $ dc
18446744073709551616 18446744073709551616 / ps
dc: big number failure 306b06b: No such file or directory
That number is 2^64. The error is coming from BN_check in bdiv(), which is complaining about the
nu
On 11/08/2012 19:32, Michiel Boland wrote:
[...]
No fix, but I see a problem in the BN_add_word function in
/usr/src/crypto/openssl/crypto/bn/bn_word.c
Small test case:-
#include
#include
int main()
{
BIGNUM *n;
n = BN_new();
BN_set_word(n, ULONG_MAX - 1);
B
On 2012-11-05 17:28, Volodymyr Kostyrko wrote:
05.11.2012 18:00, Andriy Gapon wrote:
I bet on clang 3.2.
Thank you for checking.
So how do we proceed from here?
I could just revert the MFC-es, but the functionality could be desirable to some
users. Are there any alternatives?
Dunno, clang
Hi,
Great, the test case is very useful.
I have applied the following patch to crypto/bn/bn_word.c, which fixes the
problem for me.
--- //depot/vendor/freebsd/9.1-local/src/crypto/openssl/crypto/bn/bn_word.c
2012-08-13 00:32:35.0 1000
+++
/data/scratch/janm/p4/freebsd-image-std-20
