search for: zext'd

...only metadata that can't be thrown away - do you think it feasible to have this and metadata share code, eg each be derived from some common parent class? Allowing values for attributes would also be great for implementing something Chris suggested in one of his notes: getting rid of the "zext" attribute, which means that some (eg) i16 parameter is magically zext'd to an unspecified larger type like i32, and instead having the larger type i32 be the parameter type with a "zexted from i16" attribute on it. This could be done as "zexted=i16" with your system I...

...ent int zero_one_negone(int x, int y) { if (x == y) return 0; if (x > y) return 1; return -1; } define i32 @zero_one_negone(i32, i32) { %3 = icmp eq i32 %0, %1 %4 = icmp sgt i32 %0, %1 %5 = select i1 %4, i32 1, i32 -1 %6 = select i1 %3, i32 0, i32 %5 ret i32 %6 } 3. Select and zext int negone_one_zero(int x, int y) { if (x < y) return -1; if (x > y) return 1; return 0; } define i32 @negone_one_zero(i32, i32) { %3 = icmp slt i32 %0, %1 %4 = icmp sgt i32 %0, %1 %5 = zext i1 %4 to i32 %6 = select i1 %3, i32 -1, i32 %5 ret i32 %6 } 4. Select and sext int...

Overhauling Attributes Problem ======= LTO needs a way to pass options through to different parts of the compiler. In particular, we need to pass code generation options to the back-end. The way we want to do this is via the LLVM Attributes class. In order to do that, we need to overhaul the Attributes class. The Attributes class right now isn't very extensible. After considering several