similar to: [LLVMdev] clang build (Debug+Asserts) fails with Cygwin and Mingw (ASTContext.o: File too big)

On 5/2/2014 11:41 PM, David Blaikie wrote: > Any idea what all those sections are - comdat inline functions? > No idea, as I cannot run objdump -h on a object file that I couldn't build :) Anyhow, I have an old, successful Debug+Asserts build of clang, made with Mingw also, for clang revision 206070. Apparently, the ASTContext.o file there contained 16453 sections, not 33066, as

Hi all, I find a bug in the VASTContext.h of the latest clang. I fixed it and commit a patch for it. As follows: >From 447d31176b513a03b253eb25ef314c2a3c0e428a Mon Sep 17 00:00:00 2001 From: Tsingray <tsingray at buildbot-slave-desktop.(none)> Date: Thu, 8 Mar 2012 22:11:54 +0800 Subject: [PATCH] fix a 'does not name a type' bug in VASTContext.h ---

Hi All, We have populated info in the Clang Sema i.e class Sema (include/clang/Sema/Sema.h) and like to propagate the same to Clang Codegen . Currently we are propagating through ASTContext ,where we have duplicating fields info and operation in the Sema and ASTContext . Any better way of doing the same ? Thank you ~Umesh

Hi, Recently one Windows build bot failed by my commit, because the obj file being generated is too big: C:\ps4-buildslave2\llvm-clang-x86_64-expensive-checks-win\llvm\tools\clang\unittests\AST\ASTImporterTest.cpp : fatal error C1128: number of sections exceeded object file format limit: compile with /bigobj Is there an LLVM policy to limit the maximum size of the generated obj files? If not

> -----Original Message----- > From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On > Behalf Of Aaron Ballman > Sent: Monday, September 29, 2014 4:45 PM > To: Chris Bieneman > Cc: lldb-dev at cs.uiuc.edu; cfe-dev Developers; LLVM Developers Mailing List > Subject: Re: [cfe-dev] [LLVMdev] [RFC] Raising LLVM minimum required MSVC > version to 2013

Dear All, I have a question How could I use WhileStmt class in Stmt.h http://clang.llvm.org/doxygen/Stmt_8h_source.html to implement while loop like while(i==1){} that is required to be inserted For example, Convert x++; y++; to x++; while(i=1){} y++; from the class's constructor: WhileStmt(ASTContext &C, VarDecl *Var, Expr *cond, Stmt *body,SourceLocation WL);//I know C -->

On Mon, Dec 9, 2013 at 5:18 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > Mingw switched abis with the release of gcc 4.7 > (http://gcc.gnu.org/gcc-4.7/changes.html). The main change is that now > mingw (like msvc) given thiscall calling convention to methods by > default. > > I think the last bug blocking us to support the new abi has just been > fixed.

No, we use msvc cl.exe as a compiler generating C7 debug information (here is more or less our compiler options regarding optimization/debugability): /Z7 /GL- /bigobj /Zo /utf-8 /arch:AVX /std:c++14 /Zc:inline /Zc:ternary /Zc:rvalueCast /Zc:strictStrings /O2 /MD In this list the only weird one is /bigobj, my main fear is that we might get to the limit of sections on an obj and then by adding the

Starting a new thread to loop in cfe-dev and lldb-dev. For those not following along there has been a thread on llvm-dev about moving the minimum required Visual Studio version to 2013. The motivating reason is this will allow us to take advantage of a bunch of C++11 features that are not supported by MSVC 2012. According to MSDN (http://msdn.microsoft.com/en-us/library/hh567368.aspx) the list is:

On Tue, Dec 10, 2013 at 11:58 AM, Hans Wennborg <hans at chromium.org> wrote: > It would be nice if we could make the TypePrinter not print the > calling convention if it's the default one for the ABI, but > TypePrinter doesn't have a lot of context.. no Sema, no ASTContext :/ > Does this patch fix any failures for you? It doesn't fix that test case, unfortunately.

Just got clang from head and getting: ExprConstant.cpp: In function Obool TryEvaluateBuiltinNaN(clang::ASTContext&, clang::QualType, const clang::Expr*, bool, llvm::APFloat&)¹: ExprConstant.cpp:1578: error: no matching function for call to Ollvm::StringRef::getAsInteger(int, llvm::APInt&)¹ /home/neale/LLVM/llvm/include/llvm/ADT/StringRef.h:269: note: candidates are: bool

Rasha Omar wrote: > Dear All, > > I have a question > > How could I use |WhileStmt class| in Stmt.h > > http://clang.llvm.org/doxygen/Stmt_8h_source.html > > to implement |while loop| like |while(i==1){}| that is required to be > inserted > > For example, Convert x++; y++; to x++; while(i=1){} y++; > > from the class's constructor: > >

when I compile llvm-3.3 according to the instructions in vmkit's homepage the following error occurs: llvm-3.3.src/Release+Asserts/lib/libclangAST.a(VTableBuilder.o): In function `(anonymous namespace)::VCallAndVBaseOffsetBuilder::AddVCallOffsets(clang::BaseSubobject, clang::CharUnits)': VTableBuilder.cpp:(.text+0xc6c3): undefined reference to

> There are a handful other tests failing in the same way. > > It would be nice if we could make the TypePrinter not print the > calling convention if it's the default one for the ABI, but > TypePrinter doesn't have a lot of context.. no Sema, no ASTContext :/ They are all TypePrinter failures like this one? If so I would say we should not block on it since it is a small

Hi, I'm trying to understand how clang keeps track of which declarations are called within a translation unit and decides to codegen their definitions. DeclBase.h has a markUsed to keep track of ODR use, and I think that the decl can be found from the symbol table via ASTContext.h (for example looking up a template via GetQualifiedTemplateName -> getAsTemplateDecl -> setIsUsed ). This

No, I need to use it in LLVM pass. Could it work? On 26 May 2013 10:41, Nick Lewycky <nicholas at mxc.ca> wrote: > Rasha Omar wrote: > >> Dear All, >> >> I have a question >> >> How could I use |WhileStmt class| in Stmt.h >> >> http://clang.llvm.org/doxygen/**Stmt_8h_source.html<http://clang.llvm.org/doxygen/Stmt_8h_source.html>

I 100% get that we might not like the decisions clang-format is making, but how does one overcome this when adding new code? The pre-merge checks enforce clang-formatting before commit and that's a common review comment anyway for those who didn't join the pre-merge checking group. I'm just wondering are we not all following the same guidelines? Concerns of clang-format not being good

I think we need to relax the test cases. MSVC usually prints the calling convention, and it's often useful information. Maybe we can make the diagnostic text smaller by using the __thiscall, __cdecl, __stdcall, etc keywords when printing types with LangOpts.MicrosoftExt, but it will require moving the attribute from after the identifier to before, which is exciting. On Tue, Dec 10, 2013 at

Hello Clang folks, I was using -ftime-trace to see where the compiler spends time parsing clang's own headers, and it pointed me to Type.h. Many AST headers need QualType to be complete, but they do not need the full type class hierarchy. To improve compile time, I have attempted to create a new header, QualType.h, that defines only the QualType wrapper class. I have started to transition

On Tue, Dec 10, 2013 at 3:57 PM, Reid Kleckner <rnk at google.com> wrote: > On Tue, Dec 10, 2013 at 11:58 AM, Hans Wennborg <hans at chromium.org> wrote: >> >> It would be nice if we could make the TypePrinter not print the >> calling convention if it's the default one for the ABI, but >> TypePrinter doesn't have a lot of context.. no Sema, no