rust/tests/ui-fulldeps/plugin/macro-crate-rlib.rs

// aux-build:rlib-crate-test.rs
// ignore-stage1
// ignore-cross-compile gives a different error message

#![feature(plugin)]
#![plugin(rlib_crate_test)]
//~^ ERROR: plugin `rlib_crate_test` only found in rlib format, but must be available in dylib

fn main() {}
Moved issue tests to subdirs and normalised names. 2019-03-11 19:49:17 -05:00			`// aux-build:rlib-crate-test.rs`
Support `x test --stage 1 ui-fulldeps` Nils had an excellent idea the other day: the same way that rustdoc is able to load `rustc_driver` from the sysroot, ui-fulldeps tests should also be able to load it from the sysroot. That allows us to run fulldeps tests with stage1, without having to fully rebuild the compiler twice. It does unfortunately have the downside that we're running the tests on the bootstrap compiler, not the in-tree sources, but since most of the fulldeps tests are for the API of the compiler, that seems ok. I think it's possible to extend this to `run-make-fulldeps`, but I've run out of energy for tonight. - Move `plugin` tests into a subdirectory. Plugins are loaded at runtime with `dlopen` and so require the ABI of the running compile to match the ABI of the compiler linked with `rustc_driver`. As a result they can't be supported in stage 1 and have to use `// ignore-stage1`. - Remove `ignore-stage1` from most non-plugin tests - Ignore diagnostic tests in stage 1. Even though this requires a stage 2 build to load rustc_driver, it's primarily testing the error message that the running compiler emits when the diagnostic struct is malformed. - Pass `-Zforce-unstable-if-unmarked` in stage1, not just stage2. That allows running `hash-stable-is-unstable` in stage1, since it now suggests adding `rustc_private` to enable loading the crates. - Add libLLVM.so to the stage0 target sysroot, to allow fulldeps tests that act as custom drivers to load it at runtime. - Pass `--sysroot stage0-sysroot` in compiletest so that we use the correct version of std. 2023-04-17 20:00:36 -05:00			`// ignore-stage1`
test: Try to fix a failing snapshot test This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling. 2014-07-15 16:00:37 -05:00			`// ignore-cross-compile gives a different error message`
rustc: Forbid plugin_registrar in only rlib form If a plugin registrar is available, the library must be found in dylib form, not just in rlib form. Closes #15475 2014-07-09 21:13:28 -05:00
Replace #[phase] with #[plugin] / #[macro_use] / #[no_link] 2014-12-31 22:43:46 -06:00			`#![feature(plugin)]`
Use a crate attribute to load plugins #[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change] 2015-02-06 15:56:38 -06:00			`#![plugin(rlib_crate_test)]`
rustc_metadata: Make crate loading fully speculative 2020-07-05 02:39:15 -05:00			//~^ ERROR: plugin `rlib_crate_test` only found in rlib format, but must be available in dylib
rustc: Forbid plugin_registrar in only rlib form If a plugin registrar is available, the library must be found in dylib form, not just in rlib form. Closes #15475 2014-07-09 21:13:28 -05:00
			`fn main() {}`