search for: shiftcount

...Tha 0xH format should be described in LangRef.html alongside 0xK<hex> and 0xM<hex> The code looks good though. lib/VMCore/AsmWriter.cpp The change updates Printing support for half data type, so it uses the new special 0xH<hex> form. Declaration of "int shiftcount" should be moved to smallest nesting possible, right after "if ( const ConstantFP ..." at line 710 (The code makes a lot more sense with a good comment on the definition of shiftcount. I prefer to add this comment: int shiftcount; // bit position, in the current word...

Hi David, Many thanks for the comments! > Tha 0xH format should be described in LangRef.html alongside > 0xK<hex> and 0xM<hex> Done. > Declaration of "int shiftcount" should be moved to smallest nesting > possible, right after "if ( const ConstantFP ..." at line 710 > > (The code makes a lot more sense with a good comment on the > definition > of shiftcount. I prefer to add this comment: > int shiftcount; // bit...

...> Subject: Re: [LLVMdev] [PATCH] OpenCL half support > > Hi David, > > Many thanks for the comments! > > > Tha 0xH format should be described in LangRef.html alongside > > 0xK<hex> and 0xM<hex> > Done. > > > Declaration of "int shiftcount" should be moved to smallest nesting > > possible, right after "if ( const ConstantFP ..." at line 710 > > > > (The code makes a lot more sense with a good comment on the > > definition > > of shiftcount. I prefer to add this comment: > >...

...utine; its contents need not be initialized and are + destroyed. LHS, REMAINDER and SCRATCH must be distinct. +*/ +int +APInt::tcDivide(integerPart *lhs, const integerPart *rhs, + integerPart *remainder, integerPart *srhs, + unsigned int parts) +{ + unsigned int n, shiftCount; + integerPart mask; + + assert(lhs != remainder && lhs != srhs && remainder != srhs); + + shiftCount = tcMSB(rhs, parts); + if (shiftCount == -1U) + return true; + + shiftCount = parts * integerPartWidth - shiftCount - 1; + n = shiftCount / integerPartWidth; + mask = (int...

...f support > > > > Hi David, > > > > Many thanks for the comments! > > > > > Tha 0xH format should be described in LangRef.html alongside > > > 0xK<hex> and 0xM<hex> > > Done. > > > > > Declaration of "int shiftcount" should be moved to smallest > nesting > > > possible, right after "if ( const ConstantFP ..." at line 710 > > > > > > (The code makes a lot more sense with a good comment on the > > > definition > > > of shiftcount. I prefer...

...lvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Tim Northover > In contrast, it's not quite clear what an arithmetic left-shift would > be. If you want to keep x << 1 == x*2 then the logical one already > does this. Only if the left-most (shiftcount + 1) bits are all-0 or all-1. I've used machines that distinguished logical and arithmetic left shift to detect when this condition fails (arith shift would trap). --paulr

This patch supplies software IEEE floating point support. The comment from the patch reproduced below says all there is to say. This patch contains the prior "cleanup" patch; please don't apply that one. Please let me know of any bugs. It is tested reasonably well, but until I put together random tests it's hard to have 100% confidence. Neil. /* A self-contained host- and

Hi, > There is a distinction between logical/arithmetic shift right, but why > not for shift left? The arithmetic right shift has the nice property that it preserves the fact that x >> 1 == x/2 for negative signed numbers (unlike the logical shift). Either because of this or because of other uses I can't think of right now almost all modern CPUs implement it in hardware, and

There is a distinction between logical/arithmetic shift right, but why not for shift left? I'm also a bit confused by one example in the reference manual: <result> = lshr i8 -2, 1 ; yields {i8}:result = 0x7FFFFFFF Is this an error in the manual? The result is supposed to be an i8 yet a i32 is shown. -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --