[lldb-dev] compile failure with VS 2015 Update 3
Adrian McCarthy via lldb-dev
lldb-dev at lists.llvm.org
Thu Jun 30 15:16:16 PDT 2016
I left out some words. I meant:
The answers on that StackOverflow question claim that 32-bit MSVC never
does more than 32-byte alignment *for parameters*.
On Thu, Jun 30, 2016 at 3:12 PM, Adrian McCarthy <amccarth at google.com>
> `default_stop_addr` is an `Address` which contains a
> `std::atomic<lldb::addr_t>`. The `addr_t` is a 64-bit value, so I assume
> it needs 64-bit alignment. The answers on that StackOverflow question
> claim that 32-bit MSVC never does more than 32-byte alignment. So my guess
> is that this has always been a problem, and the newer compiler is just
> better at reporting it.
> On Thu, Jun 30, 2016 at 2:56 PM, Philippe Lavoie <
> philippe.lavoie at octasic.com> wrote:
>> *From:* Adrian McCarthy [amccarth at google.com]
>> *Sent:* Thursday, June 30, 2016 5:36 PM
>> *To:* Philippe Lavoie
>> *Cc:* lldb-dev at lists.llvm.org
>> *Subject:* Re: [lldb-dev] compile failure with VS 2015 Update 3
>> Compiling for 32-bit or 64-bit?
>> This question looks relevant:
>> On Thu, Jun 30, 2016 at 1:19 PM, Philippe Lavoie via lldb-dev <
>> lldb-dev at lists.llvm.org> wrote:
>>> has anyone tried to compile LLDB with Visual Studio 2015 Update 3 ?
>>> It compiles fine with Update 2, but with Update 3 we get error messages
>>> D:\dev\llvm\tools\lldb\include\lldb/Target/Process.h(3194): error
>>> 'default_stop_addr': formal parameter with requested alignment of 8
>>> won't be aligned
>>> (compiling source file
>>> although there is no __declspec(align) on that parameter.
>>> We reported the issue to Microsoft here:
>>> lldb-dev mailing list
>>> lldb-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev