 |
 |
No, not worried :) Found this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61294 And then, the call to Info::GetSizeInBytes() (inline) can return 0 ... leading to optimizer producing a different path (and memset call) for == 0 case. And this brings up the warning that tells you you might have transposed the parameters (as people usually set memory to 0, not to 255 as we do here). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/826#issuecomment-422071289 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1