Thanks Richard! -ffreestanding takes care of the problem. -Jyotsna
-- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of >Richard Smith >Sent: Tuesday, July 02, 2013 4:55 PM >To: Jyotsna Verma >Cc: [email protected] >Subject: Re: XFAIL Headers/cxx11.cpp for Hexagon > >On Tue, Jul 2, 2013 at 1:59 PM, Jyotsna Verma <[email protected]> >wrote: >>>I would still like an explanation of the nature of the failure. Which >> header or >>>#include is problematic? Also, this isn't really a C++11 test, it's a >>>test >> for our >>>built-in headers, and even if it were, I don't see why it'd be >>>reasonable >> to >>>XFAIL C++11 tests for Hexagon. >> >> We do define __STDC_HOSTED__ for Hexagon which probably shouldn't be. >> The test includes stdint.h file from lib/Headers which in turn >> includes system stdint.h if __STDC_HOSTED__ macro is defined. In >> addition, it also requires some other system headers such as >> features.h, bits/predefs.h and gnu/stubs-32.h. There is no way for us >> to make these header files available in the build area. > >Does this help: > >Index: test/Headers/cxx11.cpp >=========================================================== >======== >--- test/Headers/cxx11.cpp (revision 185111) >+++ test/Headers/cxx11.cpp (working copy) >@@ -1,5 +1,5 @@ >-// RUN: %clang -fsyntax-only -std=c++11 %s -// RUN: %clang -fsyntax-only - >std=c++11 -fmodules %s >+// RUN: %clang -ffreestanding -fsyntax-only -std=c++11 %s // RUN: >+%clang -ffreestanding -fsyntax-only -std=c++11 -fmodules %s > > #include <stdalign.h> _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
