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, 18 insertions, 0 deletions

diff --git a/gcc/testsuite/g++.dg/parse/error25.C b/gcc/testsuite/g++.dg/parse/error25.C
new file mode 100644
index 000000000..a0fd24c3a
--- /dev/null
+++ b/gcc/testsuite/g++.dg/parse/error25.C
@@ -0,0 +1,18 @@
+// { dg-do compile }
+// { dg-options "-fshow-column -ansi -pedantic-errors -Wno-long-long" }
+// Origin: Steven Bosscher <steven at gcc dot gnu dot org>
+// PR c++/17401: ICE with invalid pure specifier
+
+// NOTE: This also tests QoI of diagnostic for invalid pure specifiers.
+//  Please do *not* relax the dg-error tests.
+
+class foo
+{
+  virtual void bar1 () = 0;
+  virtual void bar2 () = __null;  // { dg-error "32:invalid pure specifier" }
+  virtual void bar3 () = 4;       // { dg-error "27:invalid pure specifier" }
+  virtual void bar4 () = A::f;    // { dg-error "27:invalid pure specifier" }
+  virtual void bar5 () = 0l;      // { dg-error "28:invalid pure specifier" }
+  virtual void bar6 () = 00;      // { dg-error "28:invalid pure specifier" }
+  virtual void bar7 () = 0x0;     // { dg-error "29:invalid pure specifier" }
+};