search for: default_

...through but the sprinf() line doesn't. Can I somehow tell LTO to not apply to this function or line of code or file of code? (In reality this is something I am trying to do via Xcode for iOS targets.) thank you. 1. static void __attribute__((constructor))_initv1 () { 2. static char default_[] = "0000000000000000000000000000000000000000000000000000000000000000"; 3. sprintf( default_, "%lu", (unsigned long)5 ); 4. } -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201...

...are known to this mail server via NIS and ALL data is mounted accress NFS in read only mode on this machine, including ~home directories. I want to run dovecot like UW-IMAP...trying to keep it simple-->mail delivery to mbox /var/spool/mail/<username>. My /etc/dovecot.conf: I tried both default_ mail_env = INBOX:/var/spool/mail/%u:INBOX:INDEX=MEMORY with and with out the INBOX:INDEX=MEMORY I want to disable the indicies feature. We don't need it we're about 20 engineers or so who want to continue to use the /var/spool/mail mbox-the original Sendmail location. Most users are down...

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.

...that unicorn workers were dying when someone requested a url with utf-8 in it, and died in such a way that subsequent requests to that worker would get the same blank 500 page even for plain ascii urls. I''ve been able to recreate this behavior one a fresh rails project by setting Encoding.default_internal to utf-8 and very little else. I''ve created an example repo at: https://github.com/lparry/how_to_kill_a_unicorn All you need to do is hit http://localhost:8080/users/? and the unicorn worker will die with an error: "Error during failsafe response: "\xE2" from...

...tmap_clear (struct bitmap *bm) /* Return the bit(s) associated with the given block. * If the request is out of range, returns the default value. */ -static inline unsigned +static inline unsigned __attribute__((__nonnull__ (1))) bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) { BITMAP_OFFSET_BIT_MASK (bm, blk); @@ -139,7 +140,7 @@ bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) } /* As above but works with virtual disk offset in bytes. */ -static inline unsigned +static inline unsigned __attribute__((__nonnull__ (1))) bitmap_get (cons...

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.

...nbdkit_error. + */ +extern int bitmap_resize (struct bitmap *bm, uint64_t new_size); + +/* Return the bit(s) associated with the given block. + * If the request is out of range, returns the default value. + */ +static inline unsigned +bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) +{ + uint64_t blk_offset = blk / (8 / bm->bpb); + unsigned blk_bit = bm->bpb * (blk % (8 / bm->bpb)); + unsigned mask = (1 << bm->bpb) - 1; + + if (blk_offset >= bm->size) { + nbdkit_debug ("bitmap_get: block number is out of range"); + return default_;...

...nbdkit_error. + */ +extern int bitmap_resize (struct bitmap *bm, uint64_t new_size); + +/* Return the bit(s) associated with the given block. + * If the request is out of range, returns the default value. + */ +static inline unsigned +bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) +{ + uint64_t blk_offset = blk / (8 / bm->bpb); + unsigned blk_bit = bm->bpb * (blk % (8 / bm->bpb)); + unsigned mask = (1 << bm->bpb) - 1; + + if (blk_offset >= bm->size) { + nbdkit_debug ("bitmap_get: block number is out of range"); + return default_;...

...;ibpb - 1)); \ + unsigned mask = ((1 << (bm)->bpb) - 1) << blk_bit + +/* Return the bit(s) associated with the given block. + * If the request is out of range, returns the default value. + */ +static inline unsigned +bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) +{ + BITMAP_OFFSET_BIT_MASK (bm, blk); + + if (blk_offset >= bm->size) { + nbdkit_debug ("bitmap_get: block number is out of range"); + return default_; + } + + return (bm->bitmap[blk_offset] & mask) >> blk_bit; +} + +/* As above but works with virtual disk o...

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.

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

...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 relevant for certain distros that were already using _by default_ the "64bit" feature when formatting with ext4, for whichever volume size (even for "small" ones). With the release of version 1.43 of e2fsprogs (2016May), the "64bit" feature is enabled by default (quote from the release notes): "Mke2fs will now create file sy...

...itted 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] c"default_%m.profraw\00", comdat lld ignores comdats in LTO object files because it expects all comdats to have already been resolved. So we see this error. We are supposed to drop non-prevailing symbols here, but for some reason we do it only for weak symbols. That's not correct in ELF where comda...

...end)/" thanks, it > makes sense to add the colon. But, I will comment that on the W10 side > the "M" by itself is working fine. Without the ':', it has never worked for myself. > > Finally regarding the userou=. At this point I have a very simple, > _almost default_ ou structure. I have added only a "CompanyName OU" > and two (2) subOU's of the "CompanyName OU", they are > "DmnMmbrs-folder-redirection" and "DmnMmbrUsers". Only > "DmnMmbrs-folder-redirection" have any GPO's applied to it. &gt...

...r 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] c"default_%m.profraw\00", > comdat > > lld ignores comdats in LTO object files because it expects all comdats to > have already been resolved. So we see this error. > > We are supposed to drop non-prevailing symbols here, but for some reason > we do it only for weak symbols. That'...

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 <

...t bitmap_resize (struct bitmap *bm, uint64_t new_size); > + > +/* Return the bit(s) associated with the given block. > + * If the request is out of range, returns the default value. > + */ > +static inline unsigned > +bitmap_get_blk (const struct bitmap *bm, uint64_t blk, unsigned default_) > +{ > + uint64_t blk_offset = blk / (8 / bm->bpb); > + unsigned blk_bit = bm->bpb * (blk % (8 / bm->bpb)); Would using << and >> instead of / and % aid the compiler, since we know we have powers of 2 based on initialization, but the compiler might not see it loc...