[ 
https://issues.apache.org/jira/browse/DISPATCH-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874268#comment-16874268
 ] 

ASF GitHub Bot commented on DISPATCH-1375:
------------------------------------------

astitcher commented on issue #528: DISPATCH-1375 qdr_general_work_t could be 
shrinked to increase cache localty
URL: https://github.com/apache/qpid-dispatch/pull/528#issuecomment-506403613
 
 
   Proton actually supports C99ish rather than actual C99!
   Initially we chose C99, but then had to back off because the then current 
Microsoft compilers didn't support the C99 features we used.
   So we switched to compiling with C++ on Visual Studio. So we actually use 
the common subset of C99 and C++03.
   Visual Studio C compilers from VS2015 actually support enough C99 for the 
earlier Proton. However I would steer clear of C11 for another decade if you 
want to compile on VS!
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> qdr_general_work_t could be shrinked to increase cache localty
> --------------------------------------------------------------
>
>                 Key: DISPATCH-1375
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1375
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Francesco Nigro
>            Priority: Minor
>
> qdr_general_work_t fields are not used altogether and could be packed into 
> different groups to reduce size: on an 64 bit machine I'm getting 112 -> 80 
> bytes size



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to