[llvm-dev] [cfe-dev] Windows /bigobj

[Aaron Ballman via llvm-dev]

On Mon, Dec 17, 2018 at 10:19 AM Simon Pilgrim via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> rL349357 - we manually add /bigobj quite a bit to fix this sort of thing. Although I don't think anyone ever goes around to check if any entries can ever be removed again...

We usually ask the entries to be removed first and then use /bigobj
only when there's not another reasonable option. Since this is a test
file, I think it's fine to enable and move on.

~Aaron

>
> On 17/12/2018 15:12, Gábor Márton via cfe-dev wrote:
>
> 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 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
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev