search for: typemerg

...number of types as we go, which is expensive. In the proposed change, would it still be legal to write a type merging pass? For example, lets say we have %Foo = type { i32 } %Bar = type { i32 } @a = unnamed_addr constant %Foo { i32 42 } @a = unnamed_addr constant %Bar { i32 42 } The typemerge pass could turn this into @a = unnamed_addr constant {i32} { i32 42 } @b = unnamed_addr constant {i32} { i32 42 } And constmerge will then merge them as it does today. Another comment is that getting anonymous types would still be a bit expensive. Can we get away with just Named types (i...

...ive. In the > proposed change, would it still be legal to write a type merging pass? > For example, lets say we have > > %Foo = type { i32 } > %Bar = type { i32 } > @a = unnamed_addr constant %Foo { i32 42 } > @a = unnamed_addr constant %Bar { i32 42 } > > The typemerge pass could turn this into > > @a = unnamed_addr constant {i32} { i32 42 } > @b = unnamed_addr constant {i32} { i32 42 } > > And constmerge will then merge them as it does today. I don't see this as requiring a type merging pass. A better way to handle this (IMO) would be...

Several people have been proding me to write up my thoughts on how to fix the IR type system for LLVM 3.0. Here are some (fairly stream of conscious) thoughts on the matter: http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt Comments welcome! -Chris