search for: g0i

Rather than “fixing” it, it might be better to support a separate method for signed extension. My reasoning is as follows: int x = 7; llvm::PointerIntPair<double*, 3, int> pip; pip.setInt(x); There could be code out there that expects pip.getInt() to return 7 and not -1. So if you really want to set a negative and return a negative value, a separate method setSignedInt and getSignedInt

I think it'd be reasonable to model this on the same behavior as int to short to int round-tripping & not to speculate that there might be code relying on the existing behavior until there's evidence of it. I'd suggest changing the behavior & testing to see if anything breaks - and if nothing does, moving to the behavior rather than supporting both. On Wed, Apr 4, 2018 at

I'd argue that bitfield sign extensions are surprising and are usually a source of bugs. It would be much more explicit and less error prone for the user to write the sign extension if they want it. By extension, it seems good that PointerIntPair doesn't do sign extension when the type happens to be signed. On Wed, Apr 4, 2018 at 9:47 AM David Blaikie via llvm-dev < llvm-dev at

Many useful Netscape plugins don't come in Linux versions. Is it possible to make my Linux copy of Netscape use Windows-compiled plugins? If so, how?

The sign extension is correct. Otherwise setInt(-1) won’t work. If you don’t want sign extension, then use ‘unsigned’ and not ‘int’ in the template arguments. > On Apr 4, 2018, at 14:34, Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'd argue that bitfield sign extensions are surprising and are usually a source of bugs. It would be much more explicit and

I'd suggest someone try fixing this & see if it breaks anything that can't reasonably be fixed (before we go assuming this is by design/shouldn't be fixed just because it's the way it is today). On Wed, Apr 4, 2018 at 7:16 AM Riyaz Puthiyapurayil via llvm-dev < llvm-dev at lists.llvm.org> wrote: > It won't move the sign bit, so negative values won't fit,

It won't move the sign bit, so negative values won't fit, unless you have a 3 bit signed type ;) Note that if you assign negative values to and then read from a signed bit-field, you would do sign extension. So 3-bit signed types do exist in C++. It begs the question why PointerIntPair supports signed int types if it always loses the sign. Is it just to avoid signed/unsigned comparison

I do agree that sign-extension is the right thing to do. Unlike bit-fields, llvm::PointerIntPair has asserts checking that the int value is within range. So if you assign an out of range value, it should fail with an assertion: llvm::PointerIntPair<SomeType*, 3, int> pip; pip.setInt(7); // can be made to fail as the valid range // of signed 3-bit values is [-4:3] The above

...;!F:0H@("`@9FD*("`@(&5C:&\@ M)%!)1%,*?0H*"DU/4D4]>65S"G=H:6QE(%L@)$U/4D4@/2!Y97, at 73L@9&\* M("`@(&-A<V4@(B0Q(B!I;@H)+6A\+2UH96QP*0H@("`@("`@("`@("!U<V%G M90H)("`@(&5X:70@,`H)("`@(#L["@DM;GPM+6YO+7)E<W1A<G0I"@D@("`@ M1%)94E5./7EE<PH)("`@(#L["@DM=GPM+79E<F)O<V4I"@D@("`@5D520D]3 M13UY97,*"2`@("`[.PH)+6=\+2UG8V]R92D*"2`@("!'0T]213UW:6YB:6YD M9`H)("`@(#L["@DM1WPM+6=C;W)E+6%L;"D*"2`@("!'0T]213UA;&P*"2`@ M(&q...

All, using Samba as an AD (2k12) domain member in Stretch (2:4.5.12+dfsg-2+deb9u4) with tdb as default and rid as domain backend. No overlapping. Everything works fine. Setup was done as in the wiki [1]. If you're connecting from a Windows 10 client and do not add dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab winbind refresh tickets = Yes to