https://bugs.kde.org/show_bug.cgi?id=359950
--- Comment #6 from Tom Hughes <t...@compton.nu> --- Note that I didn't mean spills/reloads that valgrind's internal implementation does, but rather any spills/reloads that the original compiler generated. My understanding was that those would use the normal memory location for the variable, which as a double would only be 64 bits and hence would lose precision. Are you saying that gcc instead allocates an 80 bit temporary location for the spill to avoid losing precision? -- You are receiving this mail because: You are watching all bug changes.
