summaryrefslogtreecommitdiffstats
path: root/clang/lib/CodeGen/Mangle.h
Commit message (Collapse)AuthorAgeFilesLines
* Add support for generating (very basic) C++ destructors. These aren't called ↵Anders Carlsson2009-04-171-0/+3
| | | | | | by anything yet. llvm-svn: 69343
* Add support for mangling C++ constructors. Review appreciated (I'm looking ↵Anders Carlsson2009-04-151-0/+5
| | | | | | at you, Doug) llvm-svn: 69150
* Add support for mangling guard variables.Anders Carlsson2009-04-131-1/+4
| | | | llvm-svn: 68969
* fix several problems with asm renaming, by pulling it into the mangling code:Chris Lattner2009-03-211-0/+1
| | | | | | | | 1. it wasn't applying to definitions, only declarations, e.g. int x __asm("foo") 2. multiple definitions were conflicting, they weren't getting merged. 3. the code was duplicated in several places. llvm-svn: 67442
* Address Chris's comments regarding C++ name mangling.Douglas Gregor2009-02-181-1/+1
| | | | llvm-svn: 64984
* Add basic support for C++ name mangling according to the Itanium C++Douglas Gregor2009-02-131-0/+32
ABI to the CodeGen library. Since C++ code-generation is so incomplete, we can't exercise much of this mangling code. However, a few smoke tests show that it's doing the same thing as GCC. When C++ codegen matures, we'll extend the ABI tester to verify name-mangling as well, and complete the implementation here. At this point, the major client of name mangling is in the uses of the new "overloadable" attribute in C, which allows overloading. Any "overloadable" function in C (or in an extern "C" block in C++) will be mangled the same way that the corresponding C++ function would be mangled. llvm-svn: 64413
OpenPOWER on IntegriCloud