Re: [lldb-dev] LLDB windows build and /bigobj

2016-02-09 Thread Reid Kleckner via lldb-dev
Which object file has crossed the limit? When this has happened before,
this has usually highlighted over use of templates, which is worth fixing
because it speeds up builds on other platforms as well. If MSVC 2015
instead just happens to generate say one extra section per function, then
we should probably use bigobj.

On Tue, Feb 9, 2016 at 3:55 AM, Aidan Dodds via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Hi all,
>
> I pulled in recent changes to upstream llvm, clang and lldb and it seems
> to have tipped my windows build over the edge, and its complaining that
> my object files have exceeded the section limit.
> This error is raised while building the clang libraries.  Has anyone
> else seen this problem while doing an x64 build with with Visual Studio
> 2015?
>
> This problem can be fixed however by specifying /bigobj as a compiler
> flag.  The problem is however that this needs to be given to clang,
> which in turn inherits most of its cmake from llvm.
>
> I have attached my prospective patch for this issue, but wanted to check
> in with the lldb folk first to see if anyone has hit this issue, and if
> they would have any feedback before I submit it to llvm.
>
> Thanks,
> Aidan
>
> --
> Aidan Dodds
> staff software engineer, Debuggers
> Codeplay Software Ltd
> Level C, Argyle House, 3 Lady Lawson St.
> Edinbrgh, EH3 9DR
> Tel: 0131 466 0503
> Fax: 0131 557 6600
> Website: http://www.codeplay.com
> Twitter: https://twitter.com/codeplaysoft
>
> This email and any attachments may contain confidential and /or privileged
> information and is for use by the addressee only. If you are not the
> intended recipient, please notify Codeplay Software Ltd immediately and
> delete the message from your computer. You may not copy or forward it,or
> use or disclose its contents to any other person. Any views or other
> information in this message which do not relate to our business are not
> authorized by Codeplay software Ltd, nor does this message form part of any
> contract unless so stated.
> As internet communications are capable of data corruption Codeplay
> Software Ltd does not accept any responsibility for any changes made to
> this message after it was sent. Please note that Codeplay Software Ltd does
> not accept any liability or responsibility for viruses and it is your
> responsibility to scan any attachments.
> Company registered in England and Wales, number: 04567874
> Registered office: 81 Linkfield Street, Redhill RH1 6BY
>
>
>
>
>
>
>
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] LLDB windows build and /bigobj

2016-02-09 Thread Reid Kleckner via lldb-dev
OK, we've had to change that several times now. At this point I think we
should just enable bigobj on that specific file. I'll try to prepare a
patch.

On Tue, Feb 9, 2016 at 9:52 AM, Aidan Dodds  wrote:

> Hi Reid,
> Thanks for taking a look at this.
> Here was the full error:
>
> llvm\tools\clang\lib\ASTMatchers\Dynamic\Registry.cpp : fatal error C1128: 
> number of sections exceeded object file format limit: compile with /bigobj
>
> That file seems to have quite a bit of macro magic going on, so I'll try
> to dig deeper into this when I'm back in the office tomorrow.
>
>
> On 09/02/2016 17:11, Reid Kleckner wrote:
>
> Which object file has crossed the limit? When this has happened before,
> this has usually highlighted over use of templates, which is worth fixing
> because it speeds up builds on other platforms as well. If MSVC 2015
> instead just happens to generate say one extra section per function, then
> we should probably use bigobj.
>
> On Tue, Feb 9, 2016 at 3:55 AM, Aidan Dodds via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Hi all,
>>
>> I pulled in recent changes to upstream llvm, clang and lldb and it seems
>> to have tipped my windows build over the edge, and its complaining that
>> my object files have exceeded the section limit.
>> This error is raised while building the clang libraries.  Has anyone
>> else seen this problem while doing an x64 build with with Visual Studio
>> 2015?
>>
>> This problem can be fixed however by specifying /bigobj as a compiler
>> flag.  The problem is however that this needs to be given to clang,
>> which in turn inherits most of its cmake from llvm.
>>
>> I have attached my prospective patch for this issue, but wanted to check
>> in with the lldb folk first to see if anyone has hit this issue, and if
>> they would have any feedback before I submit it to llvm.
>>
>> Thanks,
>> Aidan
>>
>> --
>> Aidan Dodds
>> staff software engineer, Debuggers
>> Codeplay Software Ltd
>> Level C, Argyle House, 3 Lady Lawson St.
>> Edinbrgh, EH3 9DR
>> Tel: 0131 466 0503
>> Fax: 0131 557 6600
>> Website: http://www.codeplay.com
>> Twitter: https://twitter.com/codeplaysoft
>>
>> This email and any attachments may contain confidential and /or
>> privileged information and is for use by the addressee only. If you are not
>> the intended recipient, please notify Codeplay Software Ltd immediately and
>> delete the message from your computer. You may not copy or forward it,or
>> use or disclose its contents to any other person. Any views or other
>> information in this message which do not relate to our business are not
>> authorized by Codeplay software Ltd, nor does this message form part of any
>> contract unless so stated.
>> As internet communications are capable of data corruption Codeplay
>> Software Ltd does not accept any responsibility for any changes made to
>> this message after it was sent. Please note that Codeplay Software Ltd does
>> not accept any liability or responsibility for viruses and it is your
>> responsibility to scan any attachments.
>> Company registered in England and Wales, number: 04567874
>> Registered office: 81 Linkfield Street, Redhill RH1 6BY
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] LLDB windows build and /bigobj

2016-02-09 Thread Aidan Dodds via lldb-dev

Hi Reid,
Thanks for taking a look at this.
Here was the full error:

llvm\tools\clang\lib\ASTMatchers\Dynamic\Registry.cpp : fatal error C1128: 
number of sections exceeded object file format limit: compile with /bigobj

That file seems to have quite a bit of macro magic going on, so I'll try 
to dig deeper into this when I'm back in the office tomorrow.


On 09/02/2016 17:11, Reid Kleckner wrote:
Which object file has crossed the limit? When this has happened 
before, this has usually highlighted over use of templates, which is 
worth fixing because it speeds up builds on other platforms as well. 
If MSVC 2015 instead just happens to generate say one extra section 
per function, then we should probably use bigobj.


On Tue, Feb 9, 2016 at 3:55 AM, Aidan Dodds via lldb-dev 
> wrote:


Hi all,

I pulled in recent changes to upstream llvm, clang and lldb and it
seems
to have tipped my windows build over the edge, and its complaining
that
my object files have exceeded the section limit.
This error is raised while building the clang libraries. Has anyone
else seen this problem while doing an x64 build with with Visual
Studio
2015?

This problem can be fixed however by specifying /bigobj as a compiler
flag.  The problem is however that this needs to be given to clang,
which in turn inherits most of its cmake from llvm.

I have attached my prospective patch for this issue, but wanted to
check
in with the lldb folk first to see if anyone has hit this issue,
and if
they would have any feedback before I submit it to llvm.

Thanks,
Aidan

-- 
Aidan Dodds

staff software engineer, Debuggers
Codeplay Software Ltd
Level C, Argyle House, 3 Lady Lawson St.
Edinbrgh, EH3 9DR
Tel: 0131 466 0503
Fax: 0131 557 6600
Website: http://www.codeplay.com
Twitter: https://twitter.com/codeplaysoft

This email and any attachments may contain confidential and /or
privileged information and is for use by the addressee only. If
you are not the intended recipient, please notify Codeplay
Software Ltd immediately and delete the message from your
computer. You may not copy or forward it,or use or disclose its
contents to any other person. Any views or other information in
this message which do not relate to our business are not
authorized by Codeplay software Ltd, nor does this message form
part of any contract unless so stated.
As internet communications are capable of data corruption Codeplay
Software Ltd does not accept any responsibility for any changes
made to this message after it was sent. Please note that Codeplay
Software Ltd does not accept any liability or responsibility for
viruses and it is your responsibility to scan any attachments.
Company registered in England and Wales, number: 04567874
Registered office: 81 Linkfield Street, Redhill RH1 6BY








___
lldb-dev mailing list
lldb-dev@lists.llvm.org 
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev




___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev