search for: l28

...1 L16 7 1.68130480999203 12 L17 8 -1.31869519000797 13 L18 9 -2.05932766409779 14 L19 10 2.44067233590221 15 L21 13 -1.66682168482594 16 L22 14 0.0925458410842417 17 L23 15 -2.90745415891576 18 L28 19 1.09254584108424 19 L29 20 -1.90745415891576 20 L1 1 2.36694915254237 21 L2 11 -3.56101694915254 22 L3 21 3.36694915254237 23 L4 23 2.43898305084746 24 L5 24 -0.561016949152542 25 L6...

...ions --disable-sse --disable-altivec" to OPTFLAGS (see /debian/rules file inside <http://http.debian.net/debian/pool/main/f/flac/flac_1.3.1-4.debian.tar.xz> ) FreeBSD just comments out this option: <https://svnweb.freebsd.org/ports/head/audio/flac/files/patch-configure?view=markup#l28> Maybe it makes sense to remove this option? 3. What's the intended meaning of --enable-sse / --disable-sse options? What should they do/enable/disable?

...t git blame documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125 Relevant git config documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/config/blame.txt#L23-L28 -----Original Message----- From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Peter Waller via llvm-dev Sent: Tuesday, July 23, 2019 11:25 To: llvm-dev at lists.llvm.org Cc: nd <nd at arm.com> Subject: Re: [llvm-dev] RFC: changing variable naming rules in LLVM codebase &a...

...won't support 386/486/586 _processors_. It will work on i686+ CPUs, and some of them (Pentium Pro, II, III, Athlon, Athlon XP) don't support SSE2. >> FreeBSD just comments out this option: >> <https://svnweb.freebsd.org/ports/head/audio/flac/files/patch-configure?view=markup#l28> >> >> Maybe it makes sense to remove this option? > > Without knowing why FreeBSD disabled it, I'd prefer not to change it. Probably because they want to build libFLAC so that it supports older processors? >> 3. >> What's the intended meaning of --enable-...

...ew people and find how can reproduce and fix this issues. I don't have any more time I can give to this unfortunately and it would be a shame for the work to go to waste. [0] https://github.com/torvalds/linux/blob/d012a7190fc1fd72ed48911e77ca97ba4521bccd/drivers/gpu/drm/i915/i915_scatterlist.h#L28 [1] https://linuxplumbersconf.org/event/7/contributions/846/ On Fri, 29 May 2020 at 22:21, Logan Gunthorpe <logang at deltatee.com> wrote: > > > > On 2020-05-29 3:11 p.m., Marek Szyprowski wrote: > > Patches are pending: > > https://lore.kernel.org/linux-iommu/2020051...

...we are expecting to read or write (or either) to the socket. As an example, let's say we have just connected to the NBD server. We expect the NBD server to send a magic string, here: https://gitlab.com/nbdkit/libnbd/-/blob/20dceca48623835c3e8a195ef4135cce5e33efba/generator/states-magic.c#L28 For example: $ nbdkit -s null NBDMAGICIHAVEOPT <- magic string sent by the server But in this case let's say the server is slow to send the magic string. The call to recv_into_rbuf -> h->sock->ops->recv -> recv returns EWOULDBLOCK (recv_into_rbuf returns 1). Then...

...ackages > checking for Python extension suffix (PEP-3149)... .so > checking for PyCapsule_New in -lc... no > checking for PyString_AsString in -lc... no are generated by this code: https://github.com/libguestfs/libguestfs/blob/7021a234aa1496ca552ec82ff73747a302a1b80b/m4/guestfs-python.m4#L28 As you can see from the output above you are missing all of the Python development libraries (eg. ‘python3-devel’ on Fedora). On my machine with Python 3.6.2 and the correct development libraries installed I see: ... checking for python... /usr/bin/python3 checking Python version... 3.6 checking...

...n.tar.xz> > ) It does that depending on the architecture. Since Debian won't be supporting i386 for the next release, I wonder how important that is. > FreeBSD just comments out this option: > <https://svnweb.freebsd.org/ports/head/audio/flac/files/patch-configure?view=markup#l28> > > Maybe it makes sense to remove this option? Without knowing why FreeBSD disabled it, I'd prefer not to change it. > 3. > What's the intended meaning of --enable-sse / --disable-sse options? > What should they do/enable/disable? I really could not tell you without...

On 7/6/2023 7:06 PM, Nir Soffer wrote: > > - After calling for example aio_notify_read(3), can I know that the > next reading from the file descriptor would block? > > No, you have to call again aio_get_direction() and poll again until > the event happens. > Well, what I mean is: After calling aio_notify_read, if aio_get_direction returns AIO_DIRECTION_READ or

...this other than "impatient"?); Let me answer my own question. The discrepancy between my sum2() code and the internal code for base::sum() is that the latter uses LDOUBLE = long double (on some system it's only double, cf. https://github.com/wch/r-source/blob/trunk/src/nmath/nmath.h#L28-L33), whereas my sum2() code uses double. So using long double, I can reproduce the penalty of having NA_real_ with na.rm=FALSE; > sum3 <- inline::cfunction(sig=c(x="double", narm="logical"), body=' #define LDOUBLE long double double *x_ = REAL(x); int narm_ = asLo...

> On Jul 18, 2019, at 6:09 PM, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > >> On Jul 18, 2019, at 3:49 PM, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> And one more question: >> >> What is the plan of renaming variables in llvm and clang? Will it be

I'm observing that base::sum(x, na.rm=FALSE) for typeof(x) == "double" is much more time consuming when there are missing values versus when there are not. I'm observing this on both Window and Linux, but it's quite surprising to me. Currently, my main suspect is settings in on how R was built. The second suspect is my brain. I hope that someone can clarify the below

I see. Peter, you are right about the font that causes the issue. Paul, thanks for your insights. I'll bring this to the Fedora font experts to see if we can arrive at a more permanent fix. I'll report back with any conclusion. @Martin: Meanwhile, at least you have options. One is to embed the fonts, either as Peter suggested or using cairo_pdf instead. Alternatively, Peter also has shown