search for: varint

...id understand what I make wrong. What I try to do is a compare a local variable with a constant. But when I create a ICMP instruction I get that instruction are not of same type. I'm using llvm by svn repository updated at two week ago. The code that I try to generation is something like: if varInt = 1 then varInt := 10; end_if; This is my code: void *visit(integer_c *symbol) { int64_t value = GET_CVALUE(int64, symbol); if (typeid(*currentType) == typeid(get_datatype_info_c::bool_type_name)) { std::cout << "Creating integer: " << value << st...

...a compare a local variable with a constant. > But when I create a ICMP instruction I get that instruction are > not of same type. > I'm using llvm by svn repository updated at two week ago. > > The code that I try to generation is something like: > > if varInt = 1 then > varInt := 10; > end_if; > > > This is my code: > > void *visit(integer_c *symbol) { > int64_t value = GET_CVALUE(int64, symbol); > if (typeid(*currentType) == > typeid(get_datatype_info_c::bool_type_n...

...What I try to do is a compare a local variable with a constant. > But when I create a ICMP instruction I get that instruction are not of > same type. > I'm using llvm by svn repository updated at two week ago. > > The code that I try to generation is something like: > > if varInt = 1 then > varInt := 10; > end_if; > > > This is my code: > > void *visit(integer_c *symbol) { > int64_t value = GET_CVALUE(int64, symbol); > if (typeid(*currentType) == typeid(get_datatype_info_c::**bool_type_name)) > { > st...

...re a local variable with a constant. >> But when I create a ICMP instruction I get that instruction are not of >> same type. >> I'm using llvm by svn repository updated at two week ago. >> >> The code that I try to generation is something like: >> >> if varInt = 1 then >> varInt := 10; >> end_if; >> >> >> This is my code: >> >> void *visit(integer_c *symbol) { >> int64_t value = GET_CVALUE(int64, symbol); >> if (typeid(*currentType) == >> typeid(get_datatype_info_c:...

...s no reason for the original metadata node you describe to not *encode* its operands into a dense bit-packed blob of memory. We can still expose APIs that manipulate them as separate entities, and have the AsmPrinter and AsmParser map back and forth with nice human-readable forms. But even a simple varint encoding will be both smaller and faster than ascii. I guess you could make it work, but would that actually be simpler than what is proposed? If it is denser, how much denser would it have to be to justify the complexity? > Just to be clear, I still want the nice format (much like your propo...

...original metadata > node you describe to not *encode* its operands into a dense bit-packed blob > of memory. We can still expose APIs that manipulate them as separate > entities, and have the AsmPrinter and AsmParser map back and forth with > nice human-readable forms. But even a simple varint encoding will be both > smaller and faster than ascii. > > > I guess you could make it work, but would that actually be simpler than > what is proposed? If it is denser, how much denser would it have to be to > justify the complexity? > I don't think it would be more comp...

...s no reason for the original metadata node you describe to not *encode* its operands into a dense bit-packed blob of memory. We can still expose APIs that manipulate them as separate entities, and have the AsmPrinter and AsmParser map back and forth with nice human-readable forms. But even a simple varint encoding will be both smaller and faster than ascii. Just to be clear, I still want the nice format (much like your proposed format, but maybe with the numbers outside of the "s) in the textual IR, I just think we should use a more direct and efficient in-memory encoding (and in-bitcode encod...

Hi Manman (and llvmdev), I filed these two bugs to track the ideas that I was cooking: http://llvm.org/bugs/show_bug.cgi?id=17891 http://llvm.org/bugs/show_bug.cgi?id=17892 TL;DR: I'm saying we should go from: !14 = metadata !{i32 786445, metadata !1, metadata !10, metadata !"y", i32 3, i64 32, i64 32, i64 32, i32 0, metadata !13} to: !14 = metadata

...with having the text format use a symbolic thing for both extremes. It doesn't seem super important, but it seems nice. Regarding the bitcode encoding, I would consider whether one encoding is more space efficient than another. I don't recall whether we default to zero or whether we use a varint encoding in the bitcode here, but if we do, it would make sense to optimize the encoding around cross thread being the most common. I'm not really a bitcode expert, so I'd rather defer to someone who has hacked on this part of LLVM more recently there. I can try to take a look at the highe...

...a >> node you describe to not *encode* its operands into a dense bit-packed blob >> of memory. We can still expose APIs that manipulate them as separate >> entities, and have the AsmPrinter and AsmParser map back and forth with >> nice human-readable forms. But even a simple varint encoding will be both >> smaller and faster than ascii. >> >> >> I guess you could make it work, but would that actually be simpler than >> what is proposed? If it is denser, how much denser would it have to be to >> justify the complexity? >> > > I...

Hi all, Attached is a sequence of patches that changes the IR to support more than two synchronization scopes. This is still a work in progress, and these patches are only meant to start a more detailed discussion on the way forward. One big issue is the absence of any backend that actually makes use of intermediate synchronization scopes. This work is meant to be just one part of the

...------------------------------------------------------ Changes since 0.9.38: Alex Villac?s Lasso (6): oleaut32: Support for VT_DISPATCH in VarAbs. oleaut32: Support for VT_DISPATCH in VarNot. oleaut32: Support for VT_DISPATCH in VarFix. oleaut32: Support for VT_DISPATCH in VarInt. oleaut32: Support for VT_DISPATCH in VarNeg. oleaut32: Support for VT_DISPATCH in VarRound. Alexander Nicolaysen S?rnes (12): wordpad: Split code into set_caption function. wordpad: Store file name globally. wordpad: Add file saving support. wordpad: Improve fi...