public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Add testcase for const-eval issue from rust-blog Date: Fri, 23 Sep 2022 06:51:55 +0000 (GMT) [thread overview] Message-ID: <20220923065155.2E7893857B8D@sourceware.org> (raw) 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; +};
reply other threads:[~2022-09-23 6:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220923065155.2E7893857B8D@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).