https://bugs.kde.org/show_bug.cgi?id=397313
Daniel Fahlgren <dan...@fahlgren.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dan...@fahlgren.se
--- Comment #2 from Daniel Fahlgren <dan...@fahlgren.se> ---
When running with --track-origins=yes you can see where the uninitialised bytes
originated from:
==7624== Uninitialised value was created by a stack allocation
==7624== at 0x10881A: main (test.c:11)
which indicates a local variable in main is to blame. The problem is that the
FPU stack is 80 bits wide even if sizeof(long double) returns 16. After the
assignment only the first 10 bytes are initialised since floating point
instructions has been used.
Valgrind correctly reports the last 6 bytes as being uninitialised.
If you do a memset followed by an assignment the warning will go away, like:
memset(&ld1, 0, sizeof ld1);
ld1 = 1.2345e+80;
--
You are receiving this mail because:
You are watching all bug changes.
