obtained gcc-4.6.4.tar.bz2 from upstream website;upstream

verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.

downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.

if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.

1 files changed, 26 insertions, 0 deletions

diff --git a/gcc/testsuite/gcc.dg/gomp/barrier-2.c b/gcc/testsuite/gcc.dg/gomp/barrier-2.c
new file mode 100644
index 000000000..3787c35a1
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/gomp/barrier-2.c
@@ -0,0 +1,26 @@
+/* { dg-do compile } */
+
+void f1(void)
+{
+  #pragma omp barrier a		/* { dg-error "expected end of line" } */
+}
+
+/* OpenMP 2.5, section 2.7.3:
+
+   Note that because the barrier construct does not have a C language
+   statement as part of its syntax, there are some restrictions on its
+   placement within a program. The barrier directive may only be placed
+   in the program at a position where ignoring or deleting the directive
+   would result in a program with correct syntax.  */
+
+void f2(void)
+{
+  label:       /* { dg-error "label at end of compound statement" } */
+    #pragma omp barrier
+}
+
+void f3(_Bool p)
+{
+  if (p)
+    #pragma omp barrier		/* { dg-error "compound statements" } */
+}