similar to: LTO prevention help

I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>.

Should we use attribute((nonnull)) at all? There's a very interesting history of this in libvirt -- try looking at commit eefb881 plus the commits referencing eefb881 -- but it does seem to work for me using recent GCC and Clang. I only did a few functions because annotating them gets old quickly... Rich.

Hi, We recently made the switch to 1.9 for our large rails 2.3.14 project and ran into some strange behavior from the unicorns where encoding problem would cause blank 500 pages to be "randomly" served to users (we run ~10 x 5 unicorn workers behind our load balancer). We found that unicorn workers were dying when someone requested a url with utf-8 in it, and died in such a way that

Annotate some function parameters with attribute((nonnull)). Only do this for internal headers where we are sure that we will be using sufficiently recent GCC or Clang. For the public header files (ie. include/nbdkit-*.h) it may be that people building out of tree plugins are using old GCC which had problems, or even other compilers that don't support this extension at all. Libvirt has an

The problem is that ThinLTO is not dropping the non-prevailing definitions, and they end up being emitted into the object file for b.o. $ ../ra/bin/llvm-dis -o - b.o0.0.preopt.bc | grep __llvm_prof $__llvm_profile_raw_version = comdat any $__llvm_profile_filename = comdat any @__llvm_profile_raw_version = constant i64 72057594037927940, comdat @__llvm_profile_filename = constant [19 x i8]

This is exactly the same as v1: https://www.redhat.com/archives/libguestfs/2018-December/msg00004.html except that it now frees the bitmap on unload (which the old code did not - there was always a memory leak). Rich.

The cow and cache filters both use a bitmap mapping virtual disk blocks to status stored in the bitmap. The implementation of the bitmaps is very similar because one was derived from the other when the filters were implemented. The main difference is the cow filter uses a simple bitmap (one bit per block), whereas the cache filter uses two bits per block. This commit abstracts the bitmap

The cow and cache filters both use a bitmap mapping virtual disk blocks to status stored in the bitmap. The implementation of the bitmaps is very similar because one was derived from the other when the filters were implemented. The main difference is the cow filter uses a simple bitmap (one bit per block), whereas the cache filter uses two bits per block. This commit abstracts the bitmap

Thanks Peter, your patch does fix the reproducer. I filed https://bugs.llvm.org/show_bug.cgi?id=37422 to track this bug. I have no clue on how to resolve the tests - whether further cleanup is required in the code or in the tests. But if Teresa or you cannot get to it, I can, with some help, take a crack at fixing the tests. On Wed, May 9, 2018 at 11:26 AM Peter Collingbourne <peter at

The cow and cache filters both use a bitmap mapping virtual disk blocks to status stored in the bitmap. The implementation of the bitmaps is very similar because one was derived from the other when the filters were implemented. The main difference is the cow filter uses a simple bitmap (one bit per block), whereas the cache filter uses two bits per block. This commit abstracts the bitmap

I have some patches I'm working on to fix the cache filter. However this is a prelude. It should be simply pure refactoring. All tests pass still. Rich.

v1 was here: https://www.redhat.com/archives/libguestfs/2019-January/msg00008.html In v2 I have provided two patches: The first patch extends attribute((nonnull)) to most internal functions, but not to the external API. The second patch uses a macro so that attribute((format)) is only used in the public API on GCC or Clang. At least in theory these headers could be used by a C compiler which

v2: https://www.redhat.com/archives/libguestfs/2018-December/msg00039.html v2 -> v3: - Fix all the issues raised in Eric's review. - Precompute some numbers to make the calculations easier. - Calculations now use bitshifts and masks in preference to division and modulo. - Clear existing bits before setting (which fixes a bug in the cache filter). Rich.

m0<-epxression((4*theta1*theta2-theta3^2)/(2*x*theta3^2)-0.5*theta1*x) params<-all.vars(m0) this reads all the params from m0 so theta1,2 and 3 correct? params<-params[-which(params=="x")] checks which params are multiplied by x? np<-length(params) for(i in 1:6){ esp<-get(sprintf("m%d",i-1))

In ext4 / e2fsprogs, there is such a thing as "64bit" features. More than 2 years ago (2014May) there was a request to improve EXTLINUX so to support such characteristics. Without supporting this feature, EXTLINUX fails to boot (or rather it fails to be installed correctly) in ext4 when the fs includes such "64bit" characteristic(s). Back then, the request was mainly

Yes, thank you for the guidance. Regarding "*You do not put the users password here (if that is what you are trying to do): --password=PASSWORD1*" My experience has been this, no matter where I put "--password=" in the string, after the "user" as the manpage suggests or the end. When I run the create string I am asked for a "New Password:' and then

On 11/10/2020 13:59, Robert Wooden wrote: > Yes, thank you for the guidance. > > Regarding "/You do not put the users password here (if that is what > you are trying to do): --password=PASSWORD1/" > > My experience has been this, no matter where I put "--password=" in > the string, after the "user" as the manpage suggests or the end. When >

Hai, Ok, below looks ok, as Rowland also said. But i have one more thing. > > ?????? Checking file: /etc/krb5.conf > > > > [libdefaults] > > ??? dns_lookup_realm = false > > ??? dns_lookup_kdc = true > > ??? default_realm = EDM-INC.COM > > ??? default_tgs_enctypes = arcfour-hmac-md5 des-cbc-crc des-cbc-md5 > > ??? default_tkt_enctypes =

Dear It is possible to configure Samba 4.4.5 to accept queries that do not use TLS? I'm having trouble authenticating the Proxy / SquidGuard in AD Samba 4.4.5. I get this error: (squidGuard): ldap_simple_bind_s failed: Strong(er) authentication required I read the wiki Samba, the new versions are working with authentication TLS encrypted connections. It is possible to configure Samba

Adding Peter to comment on the linker resolution issue. >From adding save-temps, it looks like lld and gold are giving different resolutions to the symbols, which is presumably creating this issue: (first file is with lld and second is with gold) $ diff a.out.resolution.txt gold/ 4c4 < -r=a.o,__llvm_profile_raw_version,plx --- > -r=a.o,__llvm_profile_raw_version,l 8,9c8,9 <