The compiler sets bad krate span for plugins

[huonw]

// bad_plugin_span.rs
#![crate_type="dylib"]
#![feature(plugin_registrar, rustc_private)]

extern crate rustc;

#[plugin_registrar]
pub fn plugin_registrar(reg: &mut rustc::plugin::Registry) {
    println!("{:?}", reg.krate_span);
    reg.sess.span_err(reg.krate_span, "should point to `#[plugin(...)]`");
}

// bad_plugin_span_demo.rs
#![feature(plugin)]
#![plugin(bad_plugin_span)]

fn main() {}

$ rustc bad_plugin_span.rs && rustc -L . bad_plugin_span_demo.rs
Span { lo: BytePos(27), hi: BytePos(87), expn_id: ExpnId(4294967295) }
bad_plugin_span_demo.rs:2:1: 5:12 error: should point to `#[plugin(...)]`
bad_plugin_span_demo.rs:2 #![feature(plugin)]
bad_plugin_span_demo.rs:3 #![plugin(bad_plugin_span)]
bad_plugin_span_demo.rs:4 
bad_plugin_span_demo.rs:5 fn main() {}
error: aborting due to previous error

The krate_span field of the registry should be pointing to the place that introduces the plugin, i.e. the #[plugin(...)] but it is instead pointing to the whole file (at least, from the start of the first token to the end of the last).

[brson]

Is this still reproducible?

[brson]

Whatever. Closing because you're old, bug.