Hi Jim, > If there is no way to silence the tool, then I'd recommend hard-coding our > own "dumb copy loop" instead so that the behavior continues to match what > memcpy should have been doing.
Isn't performance/throughput a concern for this case? Mamcpy is usually highly tuned with hand-optimized SIMD assembly, most likely reverting to a simply loop will not produce nearly as good code. Br, Clemens
