search for: concreate

...* %0, %1 ; <i1> [#uses=0] ret i32 0 } In the code, LLVM unifies %rt and %rt1 to be same, and picks %rt to represent them. If I define %rt %rt1 manually, can I first define %rt by opaque and refine, and then define %rt1 as normal structures --- defining %rt1 as a 'concreate' structure by Struct::Get with the element type %rt, since %rt1 is not a recursive type 'syntatically'. But I am wondering if I need PATypeHolder to protect %rt1. Will %rt1 be deleted if LLVM finds it is same to %rt? Thanks. -- Jianzhou

...nce icmp requires operands be of same type. > > In the code, LLVM unifies %rt and %rt1 to be same, and picks %rt to > represent them. If I define %rt %rt1 manually, can I first define %rt > by opaque and refine, and then define %rt1 as normal structures --- > defining %rt1 as a 'concreate' structure by Struct::Get with the > element type %rt, since %rt1 is not a recursive type 'syntatically'. > But I am wondering if I need PATypeHolder to protect %rt1. Will %rt1 > be deleted if LLVM finds it is same to %rt? > > Thanks. > -- > Jianzhou > -- Jia...

...g to write my own migration tool, or to adapt the existing one, but I could use some assistance knowing how to do the translation. Dovecot -n for that instance is below, slightly sanitized, obviously I can change pop3_uidl_format; I also tried getting rid of pop3_reuse_xuidl: Basically, to give a concreate example, the Courier system seems to use the filename as the UIDL, with this courierpop3dsizelist: /2 45 1382654636 1199751891.13891_0.water-ox:2,Sa 2412 0:1382654636 1199927364.22870_0.fire-ox:2,S 2440 0:1382654636 1199936486.3332_0.wood-ox:2,Sa 2074 0:1382654636 1199985712.27745_0.water-ox:2,RS 4...

Hi, We have a PRI connection & when its was on test networks we had echo problems withoutside line. So I bought a TE212P card resolve the echo problem. Which did to an extent. Its using asterisk 1.2.18 & RHEL4-Update 4. But now when we are live, there is a terrible echo between 2 SIP calls. If I call the same extension from outside the voice is clear. I am not sure whats

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions