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] testsuite: Add test with missing semicolon
Date: Tue, 28 Feb 2023 22:36:54 +0000 (GMT)	[thread overview]
Message-ID: <20230228223654.719C6385840C@sourceware.org> (raw)

https://gcc.gnu.org/g:b50b73e3922081d4896cd10216c4c8f89388828f

commit b50b73e3922081d4896cd10216c4c8f89388828f
Author: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
Date:   Mon Feb 27 14:08:10 2023 +0100

    testsuite: Add test with missing semicolon
    
    Add a test to the testsuite in order to verify the presence of a
    semicolon at the end of an external type item declaration.
    
    gcc/testsuite/ChangeLog:
    
            * rust/compile/extern_type_item_missing_semi.rs: New failing
            test.
    
    Signed-off-by: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>

Diff:
---
 gcc/testsuite/rust/compile/extern_type_item_missing_semi.rs | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gcc/testsuite/rust/compile/extern_type_item_missing_semi.rs b/gcc/testsuite/rust/compile/extern_type_item_missing_semi.rs
new file mode 100644
index 00000000000..a42af02210f
--- /dev/null
+++ b/gcc/testsuite/rust/compile/extern_type_item_missing_semi.rs
@@ -0,0 +1,7 @@
+// { dg-additional-options "-fsyntax-only" }
+
+extern "C" {
+    type F;
+    type E // { dg-error "failed to parse" }
+} // { dg-error "expecting" }
+// { dg-error "failed to parse item in crate" ""  { target *-*-* } .-1 }

                 reply	other threads:[~2023-02-28 22:36 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=20230228223654.719C6385840C@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: link
Be 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).