Bug 37623 - builtin-math-4 tests fail
Summary: builtin-math-4 tests fail
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: testsuite (show other bugs)
Version: 4.3.2
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-23 13:44 UTC by Tim Van Holder
Modified: 2008-09-24 07:18 UTC (History)
2 users (show)

See Also:
Host: i686-pc-linux-gnu
Target: i686-pc-linux-gnu
Build: i686-pc-linux-gnu
Known to work:
Known to fail:
Last reconfirmed:


Attachments
Test results for "builtin-math-4.c -O3 -g" (372 bytes, text/plain)
2008-09-23 13:45 UTC, Tim Van Holder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Van Holder 2008-09-23 13:44:26 UTC
Clean build from a source tree that was the result of svn switching to the 4.3.2 release tag (was previously a 4.3.0 release I think).
make check reports a handful of errors; I'm logging each separately once I determine the likely cause.

The builtin-math-4.c test (8 flavours) from gcc.dg fails.
Lots of linker errors for link_error in the log (which looks like the expected failure type for the testcase).
Notable is all flavours except the -O0 one have linker errors other than the intentional link_error ones. In particular, the gamma_r, gammal_r, gammaf_r end up being undefined, so it looks like some not-always-builtin math routines are also included in the test.

I'll attach the error list for the test that uses -g, as there the line numbers of the link errors are included.
Comment 1 Tim Van Holder 2008-09-23 13:45:53 UTC
Created attachment 16394 [details]
Test results for "builtin-math-4.c -O3 -g"
Comment 2 Jakub Jelinek 2008-09-23 18:33:19 UTC
That probably means you have too old mpfr.
Comment 3 Eric Botcazou 2008-09-23 19:26:13 UTC
> That probably means you have too old mpfr.

Yes, I just upgraded from 2.2.x to 2.3.1 on Solaris and the failure vanished.
Comment 4 Tim Van Holder 2008-09-24 07:03:06 UTC
Then perhaps either configure should reject the too-old version, or the testcase should detect this situation and either skip the tests in question and/or report that MPFR is too old. The situation as it stands is not very helpful.
Comment 5 Eric Botcazou 2008-09-24 07:18:52 UTC
> Then perhaps either configure should reject the too-old version, or the
> testcase should detect this situation and either skip the tests in question
> and/or report that MPFR is too old. The situation as it stands is not very
> helpful.

See the comment at the beginning of the testcase.  Moreover, configure should
have reported that the version of MPFR is not optimal.