[gcc/devel/rust/master] Add testcase for const-eval issue from rust-blog
Thomas Schwinge
tschwinge@gcc.gnu.org
Fri Sep 23 06:51:55 GMT 2022
https://gcc.gnu.org/g:5f01d6c53734802955568771e75df68ffc2fd0d8
commit 5f01d6c53734802955568771e75df68ffc2fd0d8
Author: Philip Herron <philip.herron@embecosm.com>
Date: Sun Sep 18 10:37:06 2022 +0100
Add testcase for const-eval issue from rust-blog
see:
https://blog.rust-lang.org/2022/09/15/const-eval-safety-rule-revision.html
Diff:
---
gcc/testsuite/rust/compile/rust-const-blog-issue.rs | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/gcc/testsuite/rust/compile/rust-const-blog-issue.rs b/gcc/testsuite/rust/compile/rust-const-blog-issue.rs
new file mode 100644
index 00000000000..a5ea2ebacb9
--- /dev/null
+++ b/gcc/testsuite/rust/compile/rust-const-blog-issue.rs
@@ -0,0 +1,12 @@
+// { dg-excess-errors "accessing value of" }
+mod mem {
+ extern "rust-intrinsic" {
+ #[rustc_const_stable(feature = "const_transmute", since = "1.46.0")]
+ fn transmute<T, U>(_: T) -> U;
+ }
+}
+
+pub static FOO: () = unsafe {
+ let illegal_ptr2int: usize = mem::transmute(&());
+ let _copy = illegal_ptr2int;
+};
More information about the Gcc-cvs
mailing list