search for: mewplay

...e examples? To my novice eyes they seem to highlight inconsistencies in LLVM IR (or the reference implementation), but it is quite likely that I've overlooked something. Please help me out. Note: the example source files have been attached and a copy is made available at https://github.com/mewplay/ll * Item 1 - named pointer types It is possible to create a named array pointer type (and many others), but not a named structure pointer type. E.g. %x = type [1 x i32]* ; valid. %x = type {i32}* ; invalid. Is this the intended behaviour? Attaching a.ll, b.ll, c.ll and d.ll for reference...

...stencies in LLVM IR (or the reference >>> implementation), but it is quite likely that I've overlooked something. >>> Please help me out. >>> >>> Note: the example source files have been attached and a copy is made >>> available at https://github.com/mewplay/ll >>> >>> * Item 1 - named pointer types >>> >>> It is possible to create a named array pointer type (and many others), >>> but >>> not a named structure pointer type. E.g. >>> >>> %x = type [1 x i32]* ; valid. >>> %x...

...to highlight inconsistencies in LLVM IR (or the reference >> implementation), but it is quite likely that I've overlooked something. >> Please help me out. >> >> Note: the example source files have been attached and a copy is made >> available at https://github.com/mewplay/ll >> >> * Item 1 - named pointer types >> >> It is possible to create a named array pointer type (and many others), but >> not a named structure pointer type. E.g. >> >> %x = type [1 x i32]* ; valid. >> %x = type {i32}* ; invalid. >> >&g...

...at I've overlooked >>>>>>> something. >>>>>>> Please help me out. >>>>>>> >>>>>>> Note: the example source files have been attached and a copy is made >>>>>>> available at https://github.com/mewplay/ll >>>>>>> >>>>>>> * Item 1 - named pointer types >>>>>>> >>>>>>> It is possible to create a named array pointer type (and many >>>>>>> others), >>>>>>> but >>>>...