summaryrefslogtreecommitdiffstats
path: root/tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs
diff options
context:
space:
mode:
Diffstat (limited to 'tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs')
-rw-r--r--tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs19
1 files changed, 19 insertions, 0 deletions
diff --git a/tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs b/tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs
new file mode 100644
index 000000000..bfb5e539c
--- /dev/null
+++ b/tests/incremental/issue-59524-layout-scalar-valid-range-is-not-unused.rs
@@ -0,0 +1,19 @@
+// We should not see the unused_attributes lint fire for
+// rustc_layout_scalar_valid_range_start, but with this bug we are
+// seeing it fire (on subsequent runs) if incremental compilation is
+// enabled.
+
+// revisions: cfail1 cfail2
+// build-pass (FIXME(62277): could be check-pass?)
+
+#![feature(rustc_attrs)]
+#![deny(unused_attributes)]
+
+#[rustc_layout_scalar_valid_range_start(10)]
+#[rustc_layout_scalar_valid_range_end(30)]
+struct RestrictedRange(u32);
+const OKAY_RANGE: RestrictedRange = unsafe { RestrictedRange(20) };
+
+fn main() {
+ OKAY_RANGE.0;
+}