public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51616] New: [4.7 Regression] gfortran.dg/quad_2.f90 fails on hppa*-*-hpux* Date: Mon, 19 Dec 2011 00:28:00 -0000 [thread overview] Message-ID: <bug-51616-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51616 Bug #: 51616 Summary: [4.7 Regression] gfortran.dg/quad_2.f90 fails on hppa*-*-hpux* Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: danglin@gcc.gnu.org Executing on host: /test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B /test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ -B/test/gnu/gcc/objdir/hppa2. 0w-hp-hpux11.11/./libgfortran/ /test/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/quad_ 2.f90 -O0 -pedantic-errors -B/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./ libgfortran/.libs -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libgfortran/.li bs -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libgfortran/.libs -B/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libquadmath/.libs -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libquadmath/.libs -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libquadmath/.libs -lm -o ./quad_2.exe (timeout = 300)/usr/ccs/bin/ld: Unsatisfied symbols: sqrtl (first referenced in /var/tmp//cc8hxOpo.o) (code)collect2: error: ld returned 1 exit statuscompiler exited with status 1output is: /usr/ccs/bin/ld: Unsatisfied symbols: sqrtl (first referenced in /var/tmp//cc8hxOpo.o) (code) collect2: error: ld returned 1 exit status FAIL: gfortran.dg/quad_2.f90 -O0 (test for excess errors)
next reply other threads:[~2011-12-19 0:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-19 0:28 danglin at gcc dot gnu.org [this message] 2011-12-19 1:04 ` [Bug fortran/51616] " kargl at gcc dot gnu.org 2011-12-19 1:29 ` dave.anglin at bell dot net 2011-12-19 1:45 ` sgk at troutmask dot apl.washington.edu 2011-12-19 1:49 ` danglin at gcc dot gnu.org 2011-12-19 2:24 ` sgk at troutmask dot apl.washington.edu 2011-12-19 9:23 ` rguenth at gcc dot gnu.org 2011-12-19 13:13 ` dave.anglin at bell dot net 2011-12-30 15:49 ` danglin at gcc dot gnu.org 2012-01-12 6:56 ` burnus at gcc dot gnu.org 2012-01-12 7:58 ` burnus at gcc dot gnu.org 2012-01-13 18:55 ` steven at gcc dot gnu.org 2012-01-15 20:26 ` burnus at gcc dot gnu.org
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=bug-51616-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).