search for: op_s

Hi, I want to update a document. The document is identified by the document path e.g. /home/user/file.txt. To find the doc id by the path I need to assign the path to the document. In the FAQ is supposed to add the doc id (the path) as a term to the document. My idea is to at the path as a value by #define PATH_ID 0 add_value(PATH_ID, "/home/user/file.txt") and then do a query:

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe

...Ideally, of course, libopusfile would continue to work with older versions > of libopus, just with a reduced feature set. The best would be if libopus > itself provided a #define that its users could check at compile time to see > if the projection API was available. See the definition of OP_SOFT_CLIP in > opusfile's src/internal.h for the hacks I've had to do to detect other > libopus API additions (hopefully we can avoid things like that here). > I think this is relatively easy to add to libopus so I'll wrap the function calls and the #include around this #define....

Hear hear. DW_ adds no readability but AT_/TAG_/OP_/etc do. Dropping the FORM entirely is fine; I view that as a mechanical encoding thing, not relevant to the informational content. If you're debugging the encoding then it would matter, but for a random string-value attribute it really doesn't matter which of the 3 (4?) different forms was used as long as the actual string shows up

Hello all, Attached are patches for libopusenc, opusfile and opus-tools in order to provide support for Ambisonics and the Projection API for encoding/decoding channel mapping 253 and 254. Please feel free to ask any questions or give any feedback you might have. :) Cheers, Drew -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ent all reads and writes in test.cpp and call function(recordRW) in testlib.so. this is how my pass looks like - for (auto &BB : F) { for (auto &I : BB) { // Is this a load or store? Get the address. Value *Ptr = nullptr; Value *op_l = nullptr; Value *op_s = nullptr; if (auto *LI = dyn_cast<LoadInst>(&I)) { Ptr = LI->getPointerOperand(); Constant* read = ConstantInt::get(Type::getInt32Ty(M.getContext()), 0); instrument_access(Ptr, &(*LI), read, M); modified = true; } el...

...ent all reads and writes in test.cpp and call function(recordRW) in testlib.so. this is how my pass looks like - for (auto &BB : F) { for (auto &I : BB) { // Is this a load or store? Get the address. Value *Ptr = nullptr; Value *op_l = nullptr; Value *op_s = nullptr; if (auto *LI = dyn_cast<LoadInst>(&I)) { Ptr = LI->getPointerOperand(); Constant* read = ConstantInt::get(Type::getInt32Ty(M.getContext()), 0); instrument_access(Ptr, &(*LI), read, M); modified = true; } el...

...figure.ac. Ideally, of course, libopusfile would continue to work with older versions of libopus, just with a reduced feature set. The best would be if libopus itself provided a #define that its users could check at compile time to see if the projection API was available. See the definition of OP_SOFT_CLIP in opusfile's src/internal.h for the hacks I've had to do to detect other libopus API additions (hopefully we can avoid things like that here). The addition of fields to the OpusHead struct is a breaking ABI change (specifically, all callers of opus_head_parse() would need to be...

> On Jan 19, 2015, at 10:34 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Mon, Jan 19, 2015 at 10:29 AM, Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: > >> On Jan 19, 2015, at 10:26 AM, Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: >> >> >>> On Jan

[mod: Forwarded by Jeff Uphoff. I tried to mangle the headers that it appears as the original post: with an invalid return address. -- REW] A few months back, a very alpha version of bliss got posted. That shouldn''t have happened, but, it was pretty much ignored so I didn''t worry about it. But now it seems there''s a bit of a fuss about this. I''ll post the

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *