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

diff --git a/gcc/testsuite/g++.dg/overload/template4.C b/gcc/testsuite/g++.dg/overload/template4.C
new file mode 100644
index 000000000..8f00d4171
--- /dev/null
+++ b/gcc/testsuite/g++.dg/overload/template4.C
@@ -0,0 +1,24 @@
+// PR c++/35986
+// { dg-do compile }
+
+namespace
+{
+  template <int> void foo (...);	// { dg-message "foo" }
+  template <int> void bar (int, ...);	// { dg-message "bar" }
+  void baz (...);			// { dg-message "baz" }
+}
+
+template <int> void foo (...);		// { dg-message "note" }
+template <int> void bar (int, ...);	// { dg-message "note" }
+void baz (...);				// { dg-message "note" }
+
+void
+test ()
+{
+  foo <0> (0);		// { dg-error "is ambiguous" }
+  // { dg-message "candidate" "candidate note" { target *-*-* } 18 }
+  bar <1> (0, 1);	// { dg-error "is ambiguous" }
+  // { dg-message "candidate" "candidate note" { target *-*-* } 20 }
+  baz (0);		// { dg-error "is ambiguous" }
+  // { dg-message "candidate" "candidate note" { target *-*-* } 22 }
+}