From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
Tobias Burnus <burnus@net-b.de>,
gcc-patches@gcc.gnu.org, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran, committed] Add libquadmath testcase gfortran.dg/quad_2.f90
Date: Tue, 08 Nov 2011 10:33:00 -0000 [thread overview]
Message-ID: <ydd62iux6n7.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20111107210011.GA50212@troutmask.apl.washington.edu> (Steve Kargl's message of "Mon, 7 Nov 2011 13:00:11 -0800")
Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
> On Mon, Nov 07, 2011 at 09:55:48PM +0100, Eric Botcazou wrote:
>> > The test uses the largest available floating-point number - be it 8, 10
>> > or 16 - and tests for that. The checks should be thus OK for any system.
>>
>> It fails with a link failure on SPARC Solaris 8 and 9:
>>
>> FAIL: gfortran.dg/quad_2.f90 -O0 (test for excess errors)
>> Excess errors:
>> Undefined first referenced
>> symbol in file
>> sqrtl /var/tmp//ccU7N9qc.o
>> ld: fatal: Symbol referencing errors. No output written to ./quad_2.exe
>
> I suppose the obvious question is 'does libm on sparc solaris 8/9
> contain a long double sqrtl() function?' If the answer is no,
> then xfail the testcase.
Please no: sqrtl is a C99 addition, and we don't want lists of non-C99
targets in tests that require them.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-11-08 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 21:09 Tobias Burnus
2011-11-07 21:00 ` Eric Botcazou
2011-11-07 21:05 ` Steve Kargl
2011-11-08 10:33 ` Rainer Orth [this message]
2011-11-08 15:41 ` Steve Kargl
2011-11-08 16:23 ` Rainer Orth
2011-11-08 16:34 ` Janne Blomqvist
2011-11-08 16:58 ` Tobias Burnus
2011-11-08 16:34 ` Steve Kargl
2011-11-08 18:56 Dominique Dhumieres
2011-11-08 19:20 ` Steve Kargl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ydd62iux6n7.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=burnus@net-b.de \
--cc=ebotcazou@adacore.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).