Initial checkin of GCC 4.9.0 from trunk (r208799).

Change-Id: I48a3c08bb98542aa215912a75f03c0890e497dba

1 files changed, 36 insertions, 0 deletions

diff --git a/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900519_13.C b/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900519_13.C
new file mode 100644
index 000000000..6b8260d41
--- /dev/null
+++ b/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900519_13.C
@@ -0,0 +1,36 @@
+// { dg-do assemble  }
+// g++ 1.37.1 bug 900519_13
+
+// If multiple inheritance creates a situation in which a given name is
+// inherited from more than one base class, and if the inherited declarations
+// for the name are for different categories of members (e.g. object members,
+// function members, enumeral members), then g++ will (in some cases) fail
+// to flag errors when the ambiguous name is used.
+
+// cfront 2.0 passes this test.
+
+// keywords: inheritance, ambiguity resolution, members
+
+struct base_0 {
+  enum { base_member }; // { dg-message "" } candidate (26, 30)
+};
+
+struct base_1 {
+  int base_member;      // { dg-message "" } candidate (26, 34)
+};
+
+struct base_2 {
+  int base_member ();   // { dg-message "" } candidate (30, 34)
+};
+
+struct derived_0 : public base_0, public base_1 {
+  void member () { base_member; }			// { dg-error "" } 
+};
+
+struct derived_1 : public base_0, public base_2 {
+  void member () { base_member; }			// { dg-error "" } missed
+};
+
+struct derived_2 : public base_1, public base_2 {
+  void member () { base_member; }			// { dg-error "" } missed
+};