Add a "link-guard" to avoid accidentally linking to a wrong dylib at runtime.

2016-03-25T18:07:19+00:00

We want to prevent compiling something against one version of a dynamic library and then, at runtime accidentally using a different version of the dynamic library. With the old symbol-naming scheme this could not happen because every symbol had the SVH in it and you'd get an error by the dynamic linker when using the wrong version of a dylib. With the new naming scheme this isn't the case any more, so this patch adds the "link-guard" to prevent this error case. This is implemented as follows: - In every crate that we compile, we emit a function called "__rustc_link_guard__" - The body of this function contains calls to the "__rustc_link_guard" functions of all dependencies. - An executable contains a call to it's own "__rustc_link_guard" function. As a consequence the "__rustc_link_guard" function call graph mirrors the crate graph and the dynamic linker will fail if a wrong dylib is loaded somewhere because its "__rustc_link_guard" function will contain a different SVH in its name.

rmake: Get all tests passing on MSVC

2015-09-17T15:40:33+00:00

Add support for different relocation models

2014-04-06T13:06:44+00:00

Rust currently defaults to `RelocPIC` regardless. This patch adds a new codegen option that allows choosing different relocation-model. The available models are: - default (Use the target-specific default model) - static - pic - no-pic For a more detailed information use `llc --help`

rust/src/test/run-make/relocation-model, branch 1.22.1

Add a "link-guard" to avoid accidentally linking to a wrong dylib at runtime.

rmake: Get all tests passing on MSVC

Add support for different relocation models