search for: 063909

...> type mismatch. The patch below is intended to change the linker > behaviour in the presence of a function type mismatch to add a > bitcast but otherwise continue linking as normal. Your patch looks great, applied! http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080616/063909.html Sorry for the delay, -Chris

Hi, Currently if the linker encounters a pair of linkonce function definitions with different types, it raises an error of the form: llvm-ld: error: Cannot link file 'item.o.bc': Function '_ZN18st_select_lex_unit12first_selectEv' defined as both ' %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)' and ' %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)'

...the lack of tests. Unfortunately, due to the use of temporary symbols it's not clear to me how this feature can be reliably tested. Ideas are welcome. Cheers, - Ben [1] http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061511.html [2] http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-July/063909.html [3] http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-February/047514.html [4] http://www.haskell.org/pipermail/ghc-devs/2013-September/002565.html [5] https://ghc.haskell.org/trac/ghc/ticket/4213#comment:12 [6] https://github.com/bgamari/llvm/compare/symbol-offset -------------- next part ----...

...h. The patch below is intended to change the linker >> behaviour in the presence of a function type mismatch to add a >> bitcast but otherwise continue linking as normal. > > Your patch looks great, applied! > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080616/063909.html Hi, Thanks for that, Chris. Following on from this, there's a related issue with alias type mismatches - it looks like the type errors here are obsolete as there's already code below to add the necessary bitcasts, but I'm not 100% certain what the original intent was. At...