This Valgrind issue is described at http://developer.amd.com/resources/documentation-articles/knowledge-base/ In the article, it states,
The VALGRIND application verifying and debugging tool reports bugs in ACML that are false alarms. We believe this is due to one or more bugs in VALGRIND.Details and Recommendations
- Conditional jump or move depends on uninitialised value(s)
- Uninitialised value was created by a stack allocation
Has anyone in the community written a valgrind suppression file for this?