Heikki Linnakangas writes:
> On 29/05/2019 18:47, Hamlin, Garick L wrote:
>> On Wed, May 29, 2019 at 11:01:05AM -0400, Tom Lane wrote:
>>> At the same time, I'm not sure if we should just write this off as an
>>> ignorable warning. If the C compiler concludes these are dead stores
>>> it'll proba
On 29/05/2019 18:47, Hamlin, Garick L wrote:
On Wed, May 29, 2019 at 11:01:05AM -0400, Tom Lane wrote:
At the same time, I'm not sure if we should just write this off as an
ignorable warning. If the C compiler concludes these are dead stores
it'll probably optimize them away, leading to not acc
On Wed, May 29, 2019 at 11:01:05AM -0400, Tom Lane wrote:
> Michael Paquier writes:
> > On Wed, May 29, 2019 at 01:24:19PM +, Hamlin, Garick L wrote:
> >> I ran clang checker and noticed these. It looks like the
> >> sha2 implementation is trying to zero out state on exit, but
> >> clang ch
Michael Paquier writes:
> On Wed, May 29, 2019 at 01:24:19PM +, Hamlin, Garick L wrote:
>> I ran clang checker and noticed these. It looks like the
>> sha2 implementation is trying to zero out state on exit, but
>> clang checker finds at least 'a' is a dead store.
>>
>> Should we fix thi
On Wed, May 29, 2019 at 01:24:19PM +, Hamlin, Garick L wrote:
> I ran clang checker and noticed these. It looks like the
> sha2 implementation is trying to zero out state on exit, but
> clang checker finds at least 'a' is a dead store.
>
> Should we fix this?
> Is something like the attac
I ran clang checker and noticed these. It looks like the
sha2 implementation is trying to zero out state on exit, but
clang checker finds at least 'a' is a dead store.
Should we fix this?
Is something like the attached sensible?
Is there a common/better approach to zero-out in PG ?
Garick
di
