Re: [PATCH 1/2] Don't declare xcb_req as static

Eric Anholt <[email protected]>
Newsgroups gmane.comp.freedesktop.xcb
Message-ID <[email protected]>
Adam Jackson <[email protected]> writes:

> Doing so forces the compiler to allocate storage for the symbol in
> .data, which means 24 bytes of dirty data and a relocation per request
> function.
>
>    text	   data	    bss	    dec	    hex	filename
>   88888	   7136	      8	  96032	  17720	src/.libs/libxcb-glx.so.before
>   92432	    680	      8	  93120	  16bc0	src/.libs/libxcb-glx.so.after

Increasing the executed-code size by 4% here makes me nervous -- done
any performance comparison before and after?  I think that delta will
get buried under the overhead of xcb_send_request, but it would be nice
to be sure.

Is the problem just the relocations in that data?  Would pulling the
req->ext out of xcb_protocol_request and passing it as another parameter
of a new xcb_send_request variant also fix it, while letting us keep the
remainder of the xcb_protocol_request_t static?

_______________________________________________
Xcb mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/xcb
signature.asc (application/pgp-signature, 832 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE/JuuFDWp9/ZkuCBXtdYpNtH8nugFAllT4poACgkQtdYpNtH8
nuhdgg//cAI3vcEJ1lYTaUTP2xvqpA1dtKWDoJxgW5PYN14XThQV5CQIC06Ox+90
Yrv5FUB+z/eRGt7mPLwpq+xQylnUIOmysBOgsHPKdEIvK928VlAkza92WK0d+amk
zLTqK5lVu9IR53pCvz+f5DlFhPE/zO9tbXAY57y30rmI09xA7MYXgmjsd3BQcl/i
to76uqWHmhx2QPnZaFFwkGu0b8qzFHM0WWl4ZlZUujMrJCRf1YkaLyQq0tp98nzl
IBbYWe//WxriYnd3q//sizcJP1V1prQ/blkf2ZVm85oGJVB70l2QTAGgHB2NoOcT
GOrKPHhMcqUa7IbxtDu8xvFPyJNki2AsTfApkMFnI+ZLOvFayQLN5Wje9E464M7Y
COb554CAxhxNC26/kzgTYM9FNj+0LMoxIc1/lwMecLhT9Yrbiblpprogv+dFovds
qUPZ6bVG48f6nTnTxJH8huRYti06K8LPSpGhN6CQoh8A4S5C+yCHouhEh9Pa5myn
QUPqBTFbP6w0SQfVAYcmP5JlUJkGMxdewJxqnU9i60Qz09GI2D2Xe2YZ87yjyWFh
lTB10fUK01ySit3WB7nv484ID/Vsbz5tFUNTBYzA47uPJihONtSFt+5tCMg+AI3R
IXCedlDPkb8mSHPkld4OFnHch9vWiQYhepmR5AXCpHXz/Z18gQ8=
=nkvq
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.