search for: typeb

Hi all, If I have a C struct declaration like this: typedef struct typeA {...} typeB; In the type symbol table generated should it contain an entry for struct.typeA or struct.typeB? I seem to have seen both cases using the same llvm toolchain so I just wonder if I have done something wrong. Thanks, Alvin

Hi Alvin, > If I have a C struct declaration like this: > > typedef struct typeA {...} typeB; > > In the type symbol table generated should it contain an entry for struct.typeA > or struct.typeB? I seem to have seen both cases using the same llvm toolchain > so I just wonder if I have done something wrong. it doesn't matter what the name is since it has no effect on ge...

Hi Duncan, Actually what I am doing is matching up each Type with its corresponding debug info. I have checked that the debug info generated is consistent (i.e., typeA is recorded as a derived type from composite type typeB in my example), but I have seen cases where the name recorded in the Type object is typeA and sometimes typeB, that's why I am confused. Alvin Duncan Sands wrote: > Hi Alvin, > >> If I have a C struct declaration like this: >> >> typedef struct typeA {...} typeB; &g...

Hi all, I''m new to puppet (coming from cfengine). I have a question concerning recursive copy. We have about 20 different types of desktop PC installations (typeA, typeB, ...). Each type has about 10-40 different config files. What I would like to do: I have a file server with the following structure: /dist/typeA /dist/typeB /dist/typeC ... Inside /dist/typeA the config files have the same place as they should have on the client, for example /dist/typeA |-- e...

Hi, as a followup for the signature fix for mount_vfs [1], here it is a patch series to generate automatically most of the OCaml interfaces of daemon actions. Only the Lvm and Mount modules are left with hand-written interfaces. [1] https://www.redhat.com/archives/libguestfs/2018-April/msg00059.html Thanks, Pino Toscano (3): daemon: directly use Optgroups daemon: use the structs from the

...pe_for_rstringt typ) + | RBufferOut _ -> pr "string" + | RStringList (typ, _) -> pr "%s list" (type_for_rstringt typ) + | RStruct (_, typ) -> pr "Structs.%s" typ + | RStructList (_, typ) -> pr "Structs.%s list" typ + | RHashtable (typea, typeb, _) -> + pr "(%s * %s) list" (type_for_rstringt typea) (type_for_rstringt typeb) + ) + (* Generate stubs for the functions implemented in OCaml. * Basically we implement the do_<name> function here, and * have it call out to OCaml code. diff --git a/generator/daemon.m...

...pe_for_rstringt typ) + | RBufferOut _ -> pr "string" + | RStringList (typ, _) -> pr "%s list" (type_for_rstringt typ) + | RStruct (_, typ) -> pr "Structs.%s" typ + | RStructList (_, typ) -> pr "Structs.%s list" typ + | RHashtable (typea, typeb, _) -> + pr "(%s * %s) list" (type_for_rstringt typea) (type_for_rstringt typeb) + ); + pr "\n" + (* Generate stubs for the functions implemented in OCaml. * Basically we implement the do_<name> function here, and * have it call out to OCaml code. diff --gi...

Hi all, I would like to propose a new way clang would decorate vtable loads in order to handle devirtualization better. I've added *llvm-dev* also, because this can start a discussion about changing invariant.group to just invariant. PDF version of this RFC can be found here: https://drive.google.com/file/d/0B72TmzNsY6Z8ZmpOUnB5dDZfSFU/view?usp=sharing Background: Initial old design:

Hi, as a followup for the signature fix for mount_vfs [1], here it is a patch series to generate automatically all the OCaml interfaces of daemon actions. [1] https://www.redhat.com/archives/libguestfs/2018-April/msg00059.html Thanks, Pino Toscano (5): daemon: directly use Optgroups daemon: use the structs from the Structs module daemon: move Lvm.lv_canonical to new Lvm_utils module