From 1bc5aee63eb72b341f506ad058502cd0361f0d10 Mon Sep 17 00:00:00 2001 From: Ben Cheng Date: Tue, 25 Mar 2014 22:37:19 -0700 Subject: Initial checkin of GCC 4.9.0 from trunk (r208799). Change-Id: I48a3c08bb98542aa215912a75f03c0890e497dba --- .../testsuite/g++.old-deja/g++.bugs/900127_01.C | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900127_01.C (limited to 'gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900127_01.C') diff --git a/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900127_01.C b/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900127_01.C new file mode 100644 index 000000000..a066d5848 --- /dev/null +++ b/gcc-4.9/gcc/testsuite/g++.old-deja/g++.bugs/900127_01.C @@ -0,0 +1,27 @@ +// { dg-do assemble } +// g++ 1.36.1 bug 900127_01 + +// g++ often fails to detect (and issue errors for) ambiguous overload +// situations. In such cases, one of the possibilities is chosen +// (apparently arbitrarily). Errors should be issued instead. + +// Cfront 2.0 passes this test. + +// keywords: function overloading, ambiguity + +void foo (int); +int foo (void); + +typedef int (*f_ptr_t1) (void); +typedef void (*f_ptr_t2) (int); + +void bar (f_ptr_t1); // { dg-message "note" } +void bar (f_ptr_t2); // { dg-message "note" } + +void function () +{ + bar (foo); // { dg-error "ambiguous" } + // { dg-message "candidate" "candidate note" { target *-*-* } 23 } +} + +int main () { return 0; } -- cgit v1.2.3