summaryrefslogtreecommitdiffstats
path: root/llvm/test/Linker/override-with-internal-linkage.ll
Commit message (Collapse)AuthorAgeFilesLines
* Have a single way for creating unique value names.Rafael Espindola2015-11-221-2/+2
| | | | | | | | | | | We had two code paths. One would create names like "foo.1" and the other names like "foo1". For globals it is important to use "foo.1" to help C++ name demangling. For locals there is no strong reason to go one way or the other so I kept the most common mangling (foo1). llvm-svn: 253804
* Linker: Update -override testcase to check callersDuncan P. N. Exon Smith2015-04-241-11/+13
| | | | | | | | Check that `@main` is calling `@foo2` (the renamed internal function), not the `@foo` with external linkage that's been pulled in from the override file. llvm-svn: 235730
* Linker: Add flag to override linkage rulesDuncan P. N. Exon Smith2015-04-221-0/+23
Add a flag to lib/Linker (and `llvm-link`) to override linkage rules. When set, the functions in the source module *always* replace those in the destination module. The `llvm-link` option is `-override=abc.ll`. All the "regular" modules are loaded and linked first, followed by the `-override` modules. This is useful for debugging workflows where some subset of the module (e.g., a single function) is extracted into a separate file where it's optimized differently, before being merged back in. Patch by Luqman Aden! llvm-svn: 235473
OpenPOWER on IntegriCloud