[GitHub] [geode-native] pdxcodemonkey commented on pull request #372: GEODE-5770: Fixes clang-analyzer-optin.performance.Padding warning

["pdxcodemonkey (GitHub)" <gi...@apache.org>]

What exactly does this do?  It looks like you've swapped around initialization order and perhaps declaration order of a bunch of member variables in several classes.  I'm familiar with having to do this quite often to get rid of compiler warnings when using gcc, but this is Clang and referring to "performance.padding" - does this gripe if you're declaring pointers on unaligned boundaries in your class or something?  I didn't think any modern compilers did this... 

[ Full content available at: https://github.com/apache/geode-native/pull/372 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org