search for: fpconstant

On Thu, Nov 26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Hi Devang, > > Before I get to the contents of this particular patch, I have a higher-level > design question. Why is metadata stored off the LLVMContext? Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :) > That seems like > the wrong place to me, this data is all specific to the particular module. > Specifically, a single MDNode may not cross modules, and if a module is > destroyed we should eliminate all the metadata that came with it. Metadat...

Hi Devang, Before I get to the contents of this particular patch, I have a higher-level design question. Why is metadata stored off the LLVMContext? That seems like the wrong place to me, this data is all specific to the particular module. Specifically, a single MDNode may not cross modules, and if a module is destroyed we should eliminate all the metadata that came with it. So, why

...On Thu, Nov 26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > > Hi Devang, > > > > Before I get to the contents of this particular patch, I have a > higher-level > > design question. Why is metadata stored off the LLVMContext? > > Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :) > So you can build up Constants and Instructions before inserting them where they'll be used. I suppose that sounds reasonable to do for metadata too. > That seems like > > the wrong place to me, this data is all specific to the particula...

Hi All, Now, in llvm trunk we support custom metadata, which can be attached with llvm instructions. One of the user is "debugging information". This user is special (not just because it is in llvm svn tree:) because whenever debug info is available, it is likely that corresponding metadata is attached with almost all instructions. In other words, usually it is all or nothing. This

...if (CurPtr[0] >= 'K' && CurPtr[0] <= 'M') { Kind = *CurPtr++; @@ -661,18 +663,18 @@ int LLLexer::Lex0x() { CurPtr = TokStart+1; return '0'; } - + while (isxdigit(CurPtr[0])) ++CurPtr; - + if (Kind == 'J') { // HexFPConstant - Floating point constant represented in IEEE format as a // hexadecimal number for when exponential notation is not precise enough. // Float and double only. - llvmAsmlval.FPVal = new APFloat(HexToFP(TokStart+2, CurPtr)); + llvmAsmlval.FPVal = new APFloat(HexToFP(TokStart+2, CurPt...

...d after discussion. It may be desirable to insert them before the existing vector types, grouping them with the other scalar types or we may want to put them somewhere else. Literals -------- Literal complex values have special spellings '(' <fp constant> '+'|'-' <fpconstant>'i' ')': %v1 = c64 ( 5.67 + 1.56i ) %v2 = c64 ( 55.87 - 4.23i ) %v3 = c64 ( 55.87 + -4.23i ) %v4 = c32 ( 8.24e+2 + 0.0i ) %v5 = c16 ( 0.0 + 0.0i ) Note that the literal representation requires an explicit specification of the imaginary part, even if zero. A "redundant&quo...

...rouping them with the other scalar types or we may want to put them somewhere else. Similarly, the vector types may be grouped with the other vector types or somewhere else. Literals -------- Literal complex values have special spellings '(' <fp constant> '+'|'-' <fpconstant>'i' ')': %v1 = c64 ( 5.67 + 1.56i ) %v2 = c64 ( 55.87 - 4.23i ) %v3 = c64 ( 55.87 + -4.23i ) %v4 = c32 ( 8.24e+2 + 0.0i ) %v5 = c16 ( 0.0 + 0.0i ) Note that the literal representation requires an explicit specification of the imaginary part, even if zero. A "redundant&quo...

...r we may want to put them somewhere else. > Similarly, the vector types may be grouped with the other vector types or > somewhere else. > > Literals > -------- > > Literal complex values have special spellings '(' <fp constant> '+'|'-' > <fpconstant>'i' ')': > > %v1 = c64 ( 5.67 + 1.56i ) > %v2 = c64 ( 55.87 - 4.23i ) > %v3 = c64 ( 55.87 + -4.23i ) > %v4 = c32 ( 8.24e+2 + 0.0i ) > %v5 = c16 ( 0.0 + 0.0i ) > > Note that the literal representation requires an explicit specification of the > imagi...