On Tue, 5 Nov 2013, Torbjorn Granlund wrote:
> I am working on getting the GMP bignum library to work better on
> OpenBSD.
>
> With current GMP sources (GMP 5.0.x, 5.1.x, and development head) a
> 'fat' build will not work on amd64 under OpenBSD 5.3 and 5.4. With
> older version of OpenBSD (I'
On Monday, November 4, 2013, Ingo Schwarze wrote:
>
> This fixes both our own regression tests (Ottos and mine)
> and the perl-5.18 op/threads-dirh.t test.
>
> This is not particularly efficient, forcing getdents(2) for each
> readdir(3) following seekdir(3), but at least it produces correct
> resu
I am working on getting the GMP bignum library to work better on
OpenBSD.
With current GMP sources (GMP 5.0.x, 5.1.x, and development head) a
'fat' build will not work on amd64 under OpenBSD 5.3 and 5.4. With
older version of OpenBSD (I've tested 4.9, 5.0, 5.2) things work as
expected.
The probl
On Mon, Nov 04, 2013 at 10:36:39AM -0600, Adam Thompson wrote:
> On 13-11-03 02:27 PM, Loïc BLOT wrote:
> >then to explain my draft here is my own configuration, and why it could
> >be useful to set custom priorities:
> >[...]
> >Without the possibility to change the priorities (and dynamically is
Ingo Schwarze wrote on Mon, Nov 04, 2013 at 09:51:41AM +0100:
> I will send a minimal one-line patch to just fix the bug
> and do nothing else. We should get that one in quickly.
> That would also be a candidate for -stable, i think.
> I hope to come round to that tonight.
Here it is.
This fixe
On Tue, Nov 05, 2013 at 02:24:22AM +1000, David Gwynne wrote:
>
> On 5 Nov 2013, at 12:40 am, Kenneth R Westerback
> wrote:
>
> > On Sun, Nov 03, 2013 at 10:51:43PM -0500, Brad Smith wrote:
> >> LLVM errors out on the i2o code with the following warning..
> >>
> >> ../../../../dev/i2o/iop.c:23
On 13-11-03 02:27 PM, Loïc BLOT wrote:
then to explain my draft here is my own configuration, and why it could
be useful to set custom priorities:
[...]
Without the possibility to change the priorities (and dynamically is
better than recompile the kernel and change constant values, it would be
a
Could be the FBI code we were looking for!
2013/11/4 David Gwynne
>
> On 5 Nov 2013, at 12:40 am, Kenneth R Westerback
> wrote:
>
> > On Sun, Nov 03, 2013 at 10:51:43PM -0500, Brad Smith wrote:
> >> LLVM errors out on the i2o code with the following warning..
> >>
> >> ../../../../dev/i2o/iop
On 5 Nov 2013, at 12:40 am, Kenneth R Westerback wrote:
> On Sun, Nov 03, 2013 at 10:51:43PM -0500, Brad Smith wrote:
>> LLVM errors out on the i2o code with the following warning..
>>
>> ../../../../dev/i2o/iop.c:2399:42: error: comparison of unsigned expression
>> < 0 is always false [-Werro
On Sun, Nov 03, 2013 at 10:51:43PM -0500, Brad Smith wrote:
> LLVM errors out on the i2o code with the following warning..
>
> ../../../../dev/i2o/iop.c:2399:42: error: comparison of unsigned expression <
> 0 is always false [-Werror,-Wtautological-compare]
> pt->pt_nbufs < 0 || pt->p
Hi Philip,
thanks for looking at this and for your insight. The number of aspects
to keep in mind about this patch is growing, we have to disentangle.
I will send a minimal one-line patch to just fix the bug and do nothing
else. We should get that one in quickly.
That would also be a candidate
On Sat, Nov 2, 2013 at 5:48 PM, Ingo Schwarze wrote:
> Here is an updated patch which now works correctly with Otto's
> regression test, with the new test i just committed, and with
> the test from the Perl test suite Andrew pointed out, even with
> threads enabled. It also survived quite some ma
12 matches
Mail list logo
