search for: pr411

All, After 2.5 years of working on it the Symbol Tables now have no type planes and PR411 has been resolved. (Okay, I didn't work on it solid for 2.5 years :) ) This change means that all names must be unique within their scope. That is, functions and global variables must be unique within their module and instruction names must be unique within their function. Generally this is t...

Developers, As part of PR411, I have made several of the intrinsic functions non- overloaded. While the assembler and bytecode reader are backwards compatible, front-end writers should start using the non-overloaded versions of the intrinsics. The llvm-gcc has already been updated to generate the new intrinsic names. Other fro...

Hello, I have a couple of doubts, as listed below: 1. To list all the global variables in the module, I am iterating using type_iterator and for each Type I get, I am using value_iterator to iterate over Values . In the second iteration I am getting unexpected results. For each type obtained from type_iterator->second, value_iterator->first produces the same list as what

...See http://llvm.org/PR1043 for more details. 4. Reid removed the 'type planes' of LLVM 1.x. It is no longer possible to have two values with the same name in the same symbol table. This simplifies LLVM internals, allowing significant speedups. See http://llvm.org/PR411 for more information. 5. Global variables and functions in .ll files are now prefixed with @ instead of %. This fixes some long-standing ambiguity problems with some cases. See http://llvm.org/PR645 for more details. New Features: 6. Devang implemented support for Precompiled He...