search for: bigobj

...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 then I suspect the only solution is to turn on /bigobj on the build bot, right? (Of course, I could refactor the cpp file to several smaller ones, but how do I know where to cut it?) Thanks, Gabor --------------...

...ver later this week. Our investigations have shown no problems. > > We have run into a hard situation where MSVC 2012 is missing a feature > that we are currently relying on. We made some changes to ASTMatchers > to reduce the number of symbols generated in order to not require > /bigobj support (see http://reviews.llvm.org/D5485). This change > relies on function templates with default arguments, which MSVC does > not support (it generates a C4519 error in MSVC 2012), resulting in > red bots (http://bb.pgr.jp/builders/ninja-clang-i686-msc17- > R/builds/10721). I have...

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 .debug$H with llvm-objcopy we might get over the limit (I didn'...

...pe for target 'AST/.makeall' failed make[3]: *** [AST/.makeall] Error 2 ... The reason for this seems to be that the COFF object format in Windows only supports a maximum of 2^15 sections (32768) for obj files. To work around this issue, Microsoft's compiler cl has a flag called /bigobj that allocates 32 bits in order to store the number of sections (instead of 16 bits, as this standard specifies: http://msdn.microsoft.com/en-us/library/gg463119.aspx ) Also check this for /bigobj: http://msdn.microsoft.com/en-us/library/ms173499.aspx Anybody else having this problem with Mingw...

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:

...keall] Error 2 >> >> ... >> >> >> The reason for this seems to be that the COFF object format in Windows only >> supports a maximum of 2^15 sections (32768) for obj files. >> >> To work around this issue, Microsoft's compiler cl has a flag called /bigobj >> that allocates 32 bits in order to store the number of sections (instead of >> 16 bits, as this standard specifies: >> http://msdn.microsoft.com/en-us/library/gg463119.aspx ) >> >> Also check this for /bigobj: >> http://msdn.microsoft.com/en-us/library/ms17349...

Hi, We are starting to test binaries generated by lld on windows and we notices that sometimes the visual studio debugger can't see the content of variables or gets the call stack wrong for deeply nested or complex types. Did anyone else have the same problems, or any way to try to figure out what is missing? I tried llvm-pdbutil dump -symbols but there is a lot of small diferences on

...ow that some support have creeped into LLD recently, but it is still far from being complete), moreover, when assemling GHC native codegen output, GNU assembler produces peculiar non-standard COFF files (with 0x11 relocations), and finally binutils doesn't (and probably never would) support bigobj extension in the 32-bit case. Windows GHC relies heavily on GCC, especially it's runtime system's code is full of gnu-isms, but Clang has a unique ability to combine gnu-ish frontend with ms-ish backend, I've experimented a bit and have concluded that replacing GCC as a C compiler/s...

Hi, How far are we from having '-r' in the LLD COFF linker? I'd try to implement this if not too much effort is required. Any suggestions and/or pointers? Cheers, Kyra