Gordon, > Why not simply reinsert the aliased GV into the symbol table under the > alias name? In this manner, alias objects would not need to derive > from GlobalValue at all. Aliases could be stored in a list on the side > as you describe, solving the memory usage problem. The majority of > code could remain ignorant of them, The main problem is that code should not ignore them :( Also, they should be codegen'ed in some funky way, when we're needed both names: alias and it's target at one place. Such information can be unavailable if we'll put aliases in the separate table. I don't think, there is some "direct" way to query symbol table at codegen-level. However, this can be good idea: to have some module-level map, which stores alias targets.
-- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University. _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
