Oops, sorry. Ben explicitly told me that the output was machine-dependent (i.e. whether or not we could actually print the Unicode character). I guess I'll weaken the test.
Jordan On Jul 16, 2012, at 14:43 , Ted Kremenek <[email protected]> wrote: > Author: kremenek > Date: Mon Jul 16 16:43:16 2012 > New Revision: 160322 > > URL: http://llvm.org/viewvc/llvm-project?rev=160322&view=rev > Log: > This test appears to fail on win32. > > Modified: > cfe/trunk/test/FixIt/fixit-unicode.c > > Modified: cfe/trunk/test/FixIt/fixit-unicode.c > URL: > http://llvm.org/viewvc/llvm-project/cfe/trunk/test/FixIt/fixit-unicode.c?rev=160322&r1=160321&r2=160322&view=diff > ============================================================================== > --- cfe/trunk/test/FixIt/fixit-unicode.c (original) > +++ cfe/trunk/test/FixIt/fixit-unicode.c Mon Jul 16 16:43:16 2012 > @@ -1,5 +1,6 @@ > // RUN: %clang_cc1 -fsyntax-only %s 2>&1 | FileCheck -strict-whitespace %s > // RUN: %clang_cc1 -fsyntax-only -fdiagnostics-parseable-fixits %s 2>&1 | > FileCheck -check-prefix=CHECK-MACHINE %s > +// XFAIL: win32 > > struct Foo { > int bar; > > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
