To make valgrind quit complaining and, supposedly, improve protocol stream compression, padding bytes in requests generated by XCB should be zeroed before transmission.
Most issues are fixed now, but gcc auto-pads the end of the fixed-length portions of requests, and we don't get to initialize those padding bytes. So for requests with a fixed-length part that does not end on a four-byte boundary, valgrind will still warn for now. We need to have our code generator explicitly place a padding field on the end of such structures. Doing so also allows us to eliminate one iovec from every request stub, cutting the number of memcpy's in half for requests without lists. In my measurements this is a pretty good performance win for small requests.
Jamey Sharp Do you still experience this issue with newer soft ? Please check the status of your issue.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxcb/issues/32.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.