search for: basictype

...= internal constant %llvm.dbg.variable.type { i32 459008, { }* bitcast (%llvm.dbg.subprogram.type* @llvm.dbg.subprogram to { }*), i8* getelementptr inbounds ([2 x i8]* @.str8, i32 0, i32 0), { }* bitcast (%llvm.dbg.compile_unit.type* @llvm.dbg.compile_unit to { }*), i32 13, { }* bitcast (%llvm.dbg.basictype.type* @llvm.dbg.basictype to { }*) }, section "llvm.metadata" ; <%llvm.dbg.variable.type*> [#uses=1] now what I'm interested is the line number "i32 13" shown in the metadata of @llvm.dbg.variable9. I was wondering if there is a way to do so.? Thank you Samaneh --...

...-dev at lists.llvm.org Subject: DIBuilder missing interface to generate DWARF info for packed_decimal basic type. Hello, I am working on a llvm based compiler frontend in which, I am using the packed_decimal type encoding. During using the llvm DIBuilder, I found out that the interface to create BasicType with packed_decimal encoding(DW_ATE_packed_decimal), is missing all the related encoding stuff, Like (Missing) DW_AT_picture_string - should be MDString Node - not decided yet. DW_AT_decimal_sign - May be in DIflags with mask (5 distinct inputs), like FlagDSOverPunch,...

...port debug info.) Without spending much time thinking about it, my inclination would be to add a new method to DIBuilder for the decimal and scaled binary types, because the additional parameters are meaningless in any other context. You might also consider whether to add a separate subclass of DIBasicType to handling scaling and decimal attributes. The decimal and scaled types are quite unusual, and we would not want to impose additional memory cost on all basic types to support these relatively rare cases. Are you planning to support all the decimal types? I know the OpenVMS people will also wan...

...* the >C++ code necessary to recreate your module. This is especially true >since your source language is Objective-C and that has never been tried >with llvm2cpp. Hmmm. When I was trying to compile this stuff, I remember that at one point I got an error relating to a function return ...Basictype rather than ...Kindtype. The prototype and the real implementation of the function had different return types. I changed the real implementation to match the prototype and everything compiled. I wonder if this is somehow affecting the code that llvm2cpp is creating. >> llvm2cpp came from...

...alking the whole ACL to build the ACL and all ACEs as separate structures. In Ruby, I suspect walking is better/easier. ACEs. You have most of the same stuff we had - except you forgot the SID! My ACE had the following methods: type() (allow, deny, audit, alarm - the last two are used in SACLs) basicType() (I forget what this did that was different) isAllow() isDeny() flags() mask() (32 bit mask with most of the obvious things like read, write, etc) size() - in bytes, used during unpacking. who() - returns a SID objectGUID() inheritedGUID() - both for ACEs that include such, like custom access righ...