On Jan 22, 2020, Jonathan Wakely wrote:
>>> I don't think so, that wouldn't work. I think pos02 could just be
>>> removed from the test.
>> Will do.
> Thanks, OK to commit.
Thanks, here's what I tested and am about to install.
tolerate padding in mbstate_t
From
On 21/01/20 23:04 -0300, Alexandre Oliva wrote:
On Jan 21, 2020, Jonathan Wakely wrote:
On 21/01/20 21:36 -0300, Alexandre Oliva wrote:
Padding in mbstate_t objects may get the memcmp to fail.
Attempt to avoid the failure with zero initialization.
Regstrapped on x86_64-linux-gnu, and also
On Jan 21, 2020, Jonathan Wakely wrote:
> On 21/01/20 21:36 -0300, Alexandre Oliva wrote:
>>
>> Padding in mbstate_t objects may get the memcmp to fail.
>> Attempt to avoid the failure with zero initialization.
>>
>>
>> Regstrapped on x86_64-linux-gnu, and also tested on a platform that used
On 21/01/20 21:36 -0300, Alexandre Oliva wrote:
Padding in mbstate_t objects may get the memcmp to fail.
Attempt to avoid the failure with zero initialization.
Regstrapped on x86_64-linux-gnu, and also tested on a platform that used
to fail because of padding in std::mbstate_t. Ok to
Padding in mbstate_t objects may get the memcmp to fail.
Attempt to avoid the failure with zero initialization.
Regstrapped on x86_64-linux-gnu, and also tested on a platform that used
to fail because of padding in std::mbstate_t. Ok to install?
for libstdc++-v3/ChangeLog
*
