>This discussion confirms my impression, that it should be possible as an
>interim solution, to use a port for missing math functions (cephes alike
>or whatever). The port itself could warn the user about inaccuracies and
>edge-cases.
Parts of Cephes are already in ports: math/ldouble. I had plan
Holy crap, if there was ever a current example of a bikeshed, this is it. :-)
Adrian
On 30 May 2012 10:19, Mehmet Erol Sanliturk wrote:
> On Wed, May 30, 2012 at 8:51 AM, Mark Linimon wrote:
>
>> Perhaps a more general name might be appropriate so as to include
>> fixed-point problems? math
On Tuesday, May 29, 2012 7:17:01 pm Anton Shterenlikht wrote:
> On Mon, May 21, 2012 at 01:08:24PM -0400, John Baldwin wrote:
> > On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote:
> > > On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote:
> > > > On Sun, May 20, 2012 at 09
On Wed, May 30, 2012 at 11:50 AM, Garrett Cooper wrote:
> On Wed, May 30, 2012 at 11:31 AM, Larry Rosenman wrote:
>> For the last month or so, when I reboot via shtudown -r the machine
>> sits at "All Buffers Flushed", and I have to hit it with a IPMI reset.
>>
>> What can I do to help debug this
On Wed, May 30, 2012 at 11:31 AM, Larry Rosenman wrote:
> For the last month or so, when I reboot via shtudown -r the machine
> sits at "All Buffers Flushed", and I have to hit it with a IPMI reset.
>
> What can I do to help debug this?
>
> Current rev:
>
> FreeBSD borg.lerctr.org 10.0-CURRENT Fre
For the last month or so, when I reboot via shtudown -r the machine
sits at "All Buffers Flushed", and I have to hit it with a IPMI reset.
What can I do to help debug this?
Current rev:
FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #38 r236314: Wed May
30 11:10:24 CDT 2012 r...
On Wed, May 30, 2012 at 8:51 AM, Mark Linimon wrote:
> Perhaps a more general name might be appropriate so as to include
> fixed-point problems? math-libs@? numerics@?
>
> I'm sure someone will come up with a better name.
>
> mcl
>
Numerics@ is good .
Other names may be
numerical-analysis@
Perhaps a more general name might be appropriate so as to include
fixed-point problems? math-libs@? numerics@?
I'm sure someone will come up with a better name.
mcl
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On Wed, May 30, 2012 at 11:31:36PM +0800, r...@9du.org wrote:
> @pcap.c
>
> int
> pcap_inject(pcap_t *p, const void *buf, size_t size)
> {
> struct my_ring *me = p;
> u_int si;
>
> ND("cnt %d", cnt);
> /* scan all rings */
> for (si = me->begin; si < me->e
@pcap.c
int
pcap_inject(pcap_t *p, const void *buf, size_t size)
{
struct my_ring *me = p;
u_int si;
ND("cnt %d", cnt);
/* scan all rings */
for (si = me->begin; si < me->end; si++) {
struct netmap_ring *ring = NETMAP_TXRING(me->nifp, si);
On Wed, May 30, 2012 at 6:37 AM, Marcelo Araujo wrote:
> Hello fellows,
>
> Is it Dtrace broken on HEAD?
>
> root@controllerB:/sys/amd64/conf # dtrace -n 'syscall::open*:entry {
> printf("%s %s",execname,copyinstr(arg0)); }'
> *dtrace: invalid probe specifier syscall::open*:entry { printf("%s
> %s
On Wed, May 30, 2012 at 2:11 PM, HIROSHI OOTA wrote:
> Hi all,
> my PCEngine's wrap(NanoBSD, i386, 128Mbytes mem, no swap) won't start, after
> updating to r234569.
> some of daemons was killed with the message 'out of swap space'.
>
> vmstat in single user mode as:
> --- r234568(works fine)
Hi all,
my PCEngine's wrap(NanoBSD, i386, 128Mbytes mem, no swap) won't start,
after updating to r234569.
some of daemons was killed with the message 'out of swap space'.
vmstat in single user mode as:
--- r234568(works fine)
# uname -a
FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r23456
Hello fellows,
Is it Dtrace broken on HEAD?
root@controllerB:/sys/amd64/conf # dtrace -n 'syscall::open*:entry {
printf("%s %s",execname,copyinstr(arg0)); }'
*dtrace: invalid probe specifier syscall::open*:entry { printf("%s
%s",execname,copyinstr(arg0)); }: "/usr/lib/dtrace/psinfo.d", line 37:
s
On 05/29/12 19:54, Stephen Montgomery-Smith wrote:
[...]
Anyway, given that floating point is a big issue, and we are about a
decade behind schedule, really suggests that a
floating-po...@freebsd.org mailing list is needed. Or maybe there is an
existing freebsd mailing list you guys already oc
On 28/05/2012 20:45, Dimitry Andric wrote:
Note, in r236149 I have pulled in a change from upstream clang, which
should fix the root cause of the "failed to retrieve array bounds"
messages.
Indeed, I updated & rebuilt yesterday & message no-longer appeared.
Thanks
Sevan
__
16 matches
Mail list logo
