On Fri, 20 Nov 2015, David Malcolm wrote: > The source ranges are verified using the same unit-testing plugin used > for C expressions. This leads to a wart, which is that it means having > a .m test file lurking below gcc.dg/plugin. A workaround would be to > create an objc.dg/plugin subdirectory, with a new plugin.exp for testing > Objective C plugins, and having it reference the existing plugin below > gcc.dg/plugin. That seemed like excessive complication, so I went for > the simpler approach of simply putting the .m file below gcc.dg/plugin.
Have you made sure that this test is quietly not run if the --enable-languages configuration does not build the ObjC compiler? -- Joseph S. Myers jos...@codesourcery.com
