search for: l186

...pointer to the expanded version of a SEXP just like the implementation in base R does [1]. At least, VECSXP has no other measure to expose the pointer if I understand correctly. Best, Yutani [1]: https://github.com/r-devel/r-svn/blob/a3508b75d28164b0e5bcb2c87f816ce5169729a4/src/main/altclasses.c#L186 2024?6?9?(?) 10:43 luke-tierney--- via R-devel <r-devel at r-project.org>: > On Sat, 8 Jun 2024, Ben Bolker wrote: > > > The ASAN errors occur *even if the zero-length object is not actually > > accessed*/is used in a perfectly correct manner, i.e. it's perfectly &gt...

Since I've upgraded to dovecot 2.0.13 + Pigeonhole 0.2.3 (Gentoo package) I've received a few complains of users about rejected messages. Investigating the problem, I've seen that when the external sender server publishes SPF information, when some message is sent from there to one of my users that has a Sieve redirect action active to another external system (that does SPF

...t; > Of course, once the coro-split SCC pass has done all this, it must > update LLVM's representation of the call graph. It does so using ~40 > lines of code that you may read here: > https://github.com/llvm/llvm-project/blob/890c6ef1fb/llvm/lib/Transforms/Coroutines/Coroutines.cpp#L186-L224 > > To explain my understanding of the code in the above link: the > coro-split pass completely re-initializes the 'CallGraphSCC' object, > using the member function > 'CallGraphSCC::initialize(ArrayRef<CallGraphNode*>)'. The array of > nodes it uses to...

On Sat, 8 Jun 2024, Ben Bolker wrote: > The ASAN errors occur *even if the zero-length object is not actually > accessed*/is used in a perfectly correct manner, i.e. it's perfectly legal in > base R to define `m <- numeric(0)` or `m <- matrix(nrow = 0, ncol = 0)`, > whereas doing the equivalent in Rcpp will (now) lead to an ASAN error. > > i.e., these are *not*

...encountered where '==' may have been intended. w "uidlist.c",L157/C8(#257): '=' encountered where '==' may have been intended. w "uidlist.c",L174/C9(#257): '=' encountered where '==' may have been intended. w "uidlist.c",L186/C8(#257): '=' encountered where '==' may have been intended. No errors 4 warnings cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c socket.c -o socket.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated...

We?ve been seeing this a lot lately on generic CentOS 6 rpm installs: rpm -qa | grep libguestfs libguestfs-java-1.16.19-1.el6.x86_64 libguestfs-java-devel-1.16.19-1.el6.x86_64 libguestfs-1.16.19-1.el6.x86_64 libguestfs-tools-1.16.19-1.el6.x86_64 libguestfs-javadoc-1.16.19-1.el6.x86_64 libguestfs-devel-1.16.19-1.el6.x86_64 libguestfs-tools-c-1.16.19-1.el6.x86_64