search for: parsedecl

ParseDecl.cpp fails to compile with MSVC reporting the following error: ParseDecl.cpp compiler\llvm\tools\clang\lib\Parse\ParseDecl.cpp(2760) : error C2248: 'clang::A STOwningResult<Destroyer>::operator =' : cannot access private member declared i n class 'clang::ASTOwningResult<D...

...Clang 2.6 showed as follows. def err_expected_semi_declaration_chinese : Error< "您在该行声明之后是否少了个';'或者是中文输入法?">; So i append a new one in the end of file DiagnosticParseKinds.td, and then recompile it. However, there is a error occurs: llvm2.6/llvm/tools/clang/lib/Parse/ParseDecl.cpp:370: error: ‘err_expected_semi_declaration_chinese’ is not a member of ‘clang::diag’ Have any people point out whats the reason about it and how to fix it ? Thanks! Xlous zeng.

...t;private" should not be marked as a type qualifier, type specifier qualifier or declaration specifier in languages other than OpenCL. Otherwise we will end up accepting invalid C++ declarations such as: private int i; or even int private i; There are several 80-col violations in lib/Parse/ParseDecl.cpp and in the CreateIntegerAttribute function. git also picked up some trailing whitespace errors. To avoid the code duplication between ParseDeclarationSpecifiers, ParseOptionalTypeSpecifier and ParseTypeQualifierListOpt you should introduce a ParseOpenCLTypeAttributes function (e.g. see ParseB...

> -----Original Message----- > From: Peter Collingbourne [mailto:peter at pcc.me.uk] > Sent: 04 January 2011 21:42 > To: Anton Lokhmotov > Cc: cfe-dev at cs.uiuc.edu > Subject: Re: OpenCL support > > Here are my comments on the second patch. > > > +enum OpenCLAddressSpace { > > + OPENCL_PRIVATE = 0, > > + OPENCL_GLOBAL = 1, > > + OPENCL_LOCAL

...libc-2.23/assert/assert.c:92:0 #8 0x00007f72e0830dc3 (/usr/local/fbcode/gcc-5-glibc-2.23/lib/libc.so.6+0x2ddc3) #9 0x0000000005c811c6 clang::Parser::ConsumeToken() /data/users/meyering/fbsource/fbcode/llvm/build/../tools/clang/include/clang/Parse/Parser.h:324:5 #10 0x0000000005caa09b clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&, clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier, clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*) /data/users/meyering/fbsource/fbcode/llvm/tools/clang/lib/Parse/ParseDecl.cpp:0:7 #11 0x0000000005c79d61 clang::Parser::Pa...

...libc-2.23/assert/assert.c:92:0 #8 0x00007f72e0830dc3 (/usr/local/fbcode/gcc-5-glibc-2.23/lib/libc.so.6+0x2ddc3) #9 0x0000000005c811c6 clang::Parser::ConsumeToken() /data/users/meyering/fbsource/fbcode/llvm/build/../tools/clang/include/clang/Parse/Parser.h:324:5 #10 0x0000000005caa09b clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&, clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier, clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*) /data/users/meyering/fbsource/fbcode/llvm/tools/clang/lib/Parse/ParseDecl.cpp:0:7 #11 0x0000000005c79d61 clang::Parser::Pa...

In order to minimize edit/compile/debug turn time, is there a way to compile llvm tools so that the majority of the files are compiled as if for release (eg, no debug symbols), and only the handful of files that I have touched are compiled for debugging? This will reduce the load on the file system, linker and gdb tremendously. At present, AFAICT, it's all or nothing. -------------- next part

...:92:0 > #8 0x00007f72e0830dc3 (/usr/local/fbcode/gcc-5-glibc-2.23/lib/libc.so.6+0x2ddc3) > #9 0x0000000005c811c6 clang::Parser::ConsumeToken() > /data/users/meyering/fbsource/fbcode/llvm/build/../tools/clang/include/clang/Parse/Parser.h:324:5 > #10 0x0000000005caa09b > clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&, > clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier, > clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*) > /data/users/meyering/fbsource/fbcode/llvm/tools/clang/lib/Parse/ParseDecl.cpp:0:7 > #11 0x0000000005c79d...