Duncan P. N. Exon Smith 2635636165 Module: Don't rename in getOrInsertFunction() ... During LTO, user-supplied definitions of C library functions often exist. -instcombine uses Module::getOrInsertFunction() to get a handle on library functions (e.g., @puts, when optimizing @printf). Previously, Module::getOrInsertFunction() would rename any matching functions with local linkage, and create a new declaration. In LTO, this is the opposite of desired behaviour, as it skips by the user-supplied version of the library function and creates a new undefined reference which the linker often cannot resolve. After some discussing with Rafael on the list, it looks like it's undesired behaviour. If a consumer actually *needs* this behaviour, we should add new API with a more explicit name. I added two testcases: one specifically for the -instcombine behaviour and one for the LTO flow. <rdar://problem/16165191> llvm-svn: 203513		2014-03-10 23:42:28 +00:00
..
cfi_endproc.ll
current-section.ll
keep-used-puts-during-instcombine.ll	Module: Don't rename in getOrInsertFunction()	2014-03-10 23:42:28 +00:00
linkonce_odr_func.ll	Don't internalize linkonce_odr non constant variables.	2014-02-07 19:04:43 +00:00
lit.local.cfg
no-undefined-puts-when-implemented.ll	Module: Don't rename in getOrInsertFunction()	2014-03-10 23:42:28 +00:00
private-symbol.ll	Add back r201608, r201622, r201624 and r201625	2014-02-19 17:23:20 +00:00
runtime-library.ll
triple-init.ll