search for: _release

...e plenty of time, you >could even do the upgraded in more increments than I >recommended. Just be sure to read the UPDATING file each time. Now what is really recommended? Assuming I can use the CVS tags for CVSup, what should I do? Can I use the "release" tags? Like RELENG_4_0_0_RELEASE. Should I? Should I bother going to a "STABLE" version and just update my "RELEASE?" ...or, should I CVSup my machine to every "RELEASE" branch until I get to the current one. ..or should I go directly to the RELENG_4_3 and then upgrade every level of that. I don&...

...Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! The netfilter coreteam proudly presents: iptables version 1.2.9rc1 Version 1.2.9rc1 is the first release candidate of the upcoming 1.2.9 version. Please note that this is a _release candidate_ and not the final version. It is supposed to be stable, but might still contain some minor glitches. If you are testing 1.2.9rc1 and run into any bugs, please report them immediately to our bugzilla bug tracking system. The ChangeLog is attached to this mail. Version 1.2.9rc1 can be...

...long ago I remember hearing that vhost does not support file descriptor passing. Which means all of the file descriptors should be in the same process. Looking at the vhost code what I am seeing happening is that the vhost_worker persists until vhost_dev_cleanup is called from one of the vhost_???_release() functions. The release functions are only called after the last flush function completes. See __fput if you want to trace the details. On one hand this all seems reasonable. On the other hand I am not seeing the code that prevents file descriptor passing. It is probably not the worst thing...

...l letters and also start with prefix LLVM. e.g. > LLVMLTOFooBar. As we discussed, this is interface is llvm independent. It may even migrate out of include/llvm-c at some point. > 2. Do we need those #include's? We need stddef.h for size_t and stdbool.h for bool. > 4. lto_codegen_release -> lto_codegen_release_memory to be clearer > and more consistent. Renamed to lto_codegen_dispose() > 5. Use C comments /* ... */? Fixed. > 6. Please start comments with capital letters and end sentences > with periods! Or perhaps not since it'll drive Chris nuts. :-) Fixed...

...> > extern lto_symbol_attributes > lto_module_get_symbol_attribute(lto_module_t mod, uint32_t index); Why uint32_t instead of size_t? > // > // frees all memory for a code generator > // upon return the lto_code_gen_t is no longer valid > // > extern void > lto_codegen_release(lto_code_gen_t); Existing bindings use the term dispose to avoid any possible retain/ release confusion. — Gordon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080224/42e7da52/attachment.html>

...hod macros. shell32/ebrowser: Respond to IOleWindow from IExplorerBrowser. Piotr Caban (4): msvcrt: Use temp directory when creating file in tmpfile. msvcp140: Add _ContextCallback tests. msvcp140/tests: Add _TaskEventLogger tests. msvcp140: Add {_Schedule,_Reschedule,_Release}_chore implementation. Sebastian Lackner (1): ntoskrnl.exe: Add KeReleaseInStackQueuedSpinLock stub. Stefan Dösinger (3): ws2_32: Don't post completion packet if receiving fails with error immediately. iphlpapi: Implement if_nametoindex. msvcp140: Implement _To_wide....

On 05/22, Oleg Nesterov wrote: > > Right now I think that "int dead" should die, No, probably we shouldn't call get_signal() if we have already dequeued SIGKILL. > but let me think tomorrow. May be something like this... I don't like it but I can't suggest anything better right now. bool killed = false; for (;;) { ... node =

Hi all, Although [smp_]read_barrier_depends() became part of READ_ONCE() in commit 76ebbe78f739 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()"), it still limps on in the Linux memory model with the sinister hope of attracting innocent new users so that it becomes impossible to remove altogether. Let's strike before it's too late: there's only

...wind handlers on intermediate frames during virtual unwind. mshtml: Decrement refcount in nsWeakReference::Release (Valgrind). msxml3/tests: Free ready state BSTR (Valgrind). François Gouget (5): wined3d: Fix a trailing new-line in an ERR() message. ddraw: Make ddraw_surface_release_iface() static. readme: Note that Wine may also use Mac APIs. readme: Adjust a couple of section separators. readme: Update and rewrap the French translation. Gijs Vermeulen (3): msvcrt: Add stub for Concurrency::Alloc. msvcrt: Add stub for Concurrency::Free. ms...

...an object file from memory // returns NULL on error (check lto_get_error_message() for details) // extern lto_module_t lto_module_create_from_memory(const uint8_t* mem, size_t length); // // frees all memory for a module // upon return the lto_module_t is no longer valid // extern void lto_module_release(lto_module_t mod); // // returns triplet string which the object module was compiled under // extern const char* lto_module_get_target_triplet(lto_module_t mod); // // returns the number of symbols in the object module // extern uint32_t lto_module_get_num_symbols(lto_module_t mod); // // ret...

Hi all, This is version three of the patches I previously posted here: v1: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ v2: https://lore.kernel.org/r/20200630173734.14057-1-will at kernel.org Changes since v2 include: * Actually add the barrier in READ_ONCE() for Alpha! * Implement Alpha's smp_load_acquire() using __READ_ONCE(), rather than the other

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The