|
From: <sv...@va...> - 2015-08-02 19:35:56
|
Author: florian
Date: Sun Aug 2 20:35:49 2015
New Revision: 15471
Log:
Silence a few warnings issued by GCC 5.1 claiming that 'res' is
uninitialised. Perhaps an incorrect clobber or a compiler bug?
Anyhow, initialising the variable will do the trick.
Modified:
trunk/memcheck/tests/x86/fprem.c
Modified: trunk/memcheck/tests/x86/fprem.c
==============================================================================
--- trunk/memcheck/tests/x86/fprem.c (original)
+++ trunk/memcheck/tests/x86/fprem.c Sun Aug 2 20:35:49 2015
@@ -6,7 +6,7 @@
double do_fprem ( void )
{
- double res;
+ double res = 0.0;
__asm__ __volatile__(
"ffree %%st(0)\n\t"
"ffree %%st(1)\n\t"
@@ -21,7 +21,7 @@
double do_fprem1 ( void )
{
- double res;
+ double res = 0.0;
__asm__ __volatile__(
"ffree %%st(0)\n\t"
"ffree %%st(1)\n\t"
@@ -36,7 +36,7 @@
double do_fsincos ( void )
{
- double res;
+ double res = 0.0;
__asm__ __volatile__(
"fldln2\n\t"
"fsincos\n\t"
|