OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Store float for pow result test 

Optimizing gcc.dg/torture/pr41094.c, the compiler computes the
constant value and short-circuits the whole thing.  At -O0, however,
on 32-bit x86, the call to pow() remains, and the program compares the
returned value in a stack register, with excess precision, with the
exact return value expected from pow().  If libm's pow() returns a
slightly off result, the compare fails.  If the value in the register
is stored in a separate variable, so it gets rounded to double
precision, and then compared, the compare passes.

It's not clear that the test was meant to detect libm's reliance on
rounding off the excess precision, but I guess it wasn't, so I propose
this slight change that enables it to pass regardless of the slight
inaccuracy of the C library in use.


for  gcc/testsuite/ChangeLog

	* gcc.dg/torture/pr41094.c: Introduce intermediate variable.

From-SVN: r276404
This commit is contained in:
Alexandre Oliva 2019-10-01 11:36:47 +00:00 committed by Alexandre Oliva
parent 31632e2c43
commit 676e38c2a9
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gcc/testsuite/ChangeLog
View File

@ -1,5 +1,7 @@
2019-10-01 Alexandre Oliva <oliva@adacore.com>
* gcc.dg/torture/pr41094.c: Introduce intermediate variable.
PR debug/91507
* gcc.dg/debug/dwarf2/array-0.c: New.
* gcc.dg/debug/dwarf2/array-1.c: New.

3
gcc/testsuite/gcc.dg/torture/pr41094.c
View File

@ -13,7 +13,8 @@ double foo(void)
int main()
{
if (foo() != 2.0)
double r = foo ();
if (r != 2.0)
abort ();
return 0;
}