On 12/5/2014 5:26 PM, Thomas Monjalon wrote: > 2014-12-05 05:34, Qiu, Michael: >> Any comments about this version? a new workaround solution :) > Yes, one comment: I think it's ugly :) > These aliasing errors are not reliable so I think we can disable it (like > Linux does). > But in case you don't want to disable the warning, please add a comment to > your > workaround to explain it is caused by GCC strict-aliasing check.
Yes, really ugly .... But lots of reviewer voted against with disable it as my first version is disable. I could not think out a better solution for all reviewers can accept. I will add the comment with the thread of v3 patch. Thanks, Michael >>> - const uint16_t *u16 = (const uint16_t *)buf; >>> + uintptr_t ptr = (uintptr_t)buf; >>> + const uint16_t *u16 = (const uint16_t *)ptr; > Thanks
