[Bug objc++/60398] New: [4.9 Regression] FAIL: obj-c++.dg/invalid-method-2.mm -fgnu-runtime (test for errors, line 10)
ubizjak at gmail dot com
gcc-bugzilla@gcc.gnu.org
Mon Mar 3 08:14:00 GMT 2014
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60398
Bug ID: 60398
Summary: [4.9 Regression] FAIL: obj-c++.dg/invalid-method-2.mm
-fgnu-runtime (test for errors, line 10)
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: objc++
Assignee: unassigned at gcc dot gnu.org
Reporter: ubizjak at gmail dot com
Recent regression in obj-c++ testsuite [1]:
FAIL: obj-c++.dg/invalid-method-2.mm -fgnu-runtime (test for errors, line 10)
FAIL: obj-c++.dg/invalid-method-2.mm -fgnu-runtime (test for errors, line 14)
FAIL: obj-c++.dg/invalid-method-2.mm -fgnu-runtime (test for excess errors)
Compiler version: 4.9.0 20140228 (experimental) [trunk revision 208223] (GCC)
[1] http://gcc.gnu.org/ml/gcc-testresults/2014-03/msg00166.html
The compiler generates different warnings:
output is:
/home/uros/gcc-svn/trunk/gcc/testsuite/obj-c++.dg/invalid-method-2.mm:10:4:
error: 'x' does not name a type^M
/home/uros/gcc-svn/trunk/gcc/testsuite/obj-c++.dg/invalid-method-2.mm:14:18:
error: 'x' does not name a type^M
while the testcase in both cases expects:
/* { dg-error "expected" } */
More information about the Gcc-bugs
mailing list