public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/24432] [4.1 regression] Missing symbols
Date: Wed, 19 Oct 2005 14:23:00 -0000	[thread overview]
Message-ID: <20051019142308.3838.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24432-226@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from ebotcazou at gcc dot gnu dot org  2005-10-19 14:23 -------
Much better, only 8 remaining failures:

Running /home/eric/cvs/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/large_real_kind_2.F90  -O0  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O0  compilation failed to produce
executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O1  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O1  compilation failed to produce
executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O2  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O2  compilation failed to produce
executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer  (test for
excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer 
compilation failed to produce executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer
-funroll-loops  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer
-funroll-loops  compilation failed to produce executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  compilation failed to produce executable
FAIL: gfortran.dg/large_real_kind_2.F90  -O3 -g  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -O3 -g  compilation failed to
produce executable
FAIL: gfortran.dg/large_real_kind_2.F90  -Os  (test for excess errors)
WARNING: gfortran.dg/large_real_kind_2.F90  -Os  compilation failed to produce
executable

Undefined                       first referenced^M
 symbol                             in file^M
cexpl                               /var/tmp//ccDZzOIe.o^M
ccosl                               /var/tmp//ccDZzOIe.o^M
csqrtl                              /var/tmp//ccDZzOIe.o^M
asinhl                              /var/tmp//ccDZzOIe.o^M
expl                                /var/tmp//ccDZzOIe.o^M
cosl                                /var/tmp//ccDZzOIe.o^M
erfcl                               /var/tmp//ccDZzOIe.o^M
cpowl                               /var/tmp//ccDZzOIe.o^M
csinl                               /var/tmp//ccDZzOIe.o^M
sqrtl                               /var/tmp//ccDZzOIe.o^M
coshl                               /var/tmp//ccDZzOIe.o^M
sinl                                /var/tmp//ccDZzOIe.o^M
atanhl                              /var/tmp//ccDZzOIe.o^M
clogl                               /var/tmp//ccDZzOIe.o^M
atanl                               /var/tmp//ccDZzOIe.o^M
logl                                /var/tmp//ccDZzOIe.o^M
sinhl                               /var/tmp//ccDZzOIe.o^M
erfl                                /var/tmp//ccDZzOIe.o^M
acosl                               /var/tmp//ccDZzOIe.o^M
cabsl                               /var/tmp//ccDZzOIe.o^M
acoshl                              /var/tmp//ccDZzOIe.o^M
tanhl                               /var/tmp//ccDZzOIe.o^M
tanl                                /var/tmp//ccDZzOIe.o^M
asinl                               /var/tmp//ccDZzOIe.o^M

However I see that large_real_kind_2.F90 was added alongside the patch.  What's
the correct approach to fixing that?  Enhancing again c99_functions?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24432


  parent reply	other threads:[~2005-10-19 14:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 17:22 [Bug libfortran/24432] New: " ebotcazou at gcc dot gnu dot org
2005-10-18 18:05 ` [Bug libfortran/24432] " pinskia at gcc dot gnu dot org
2005-10-18 21:43 ` fxcoudert at gmail dot com
2005-10-18 21:59 ` ebotcazou at gcc dot gnu dot org
2005-10-18 22:09 ` gdr at integrable-solutions dot net
2005-10-19  8:23 ` cvs-commit at gcc dot gnu dot org
2005-10-19  8:27 ` fxcoudert at gmail dot com
2005-10-19  9:09 ` ebotcazou at gcc dot gnu dot org
2005-10-19  9:45 ` cvs-commit at gcc dot gnu dot org
2005-10-19  9:46 ` fxcoudert at gmail dot com
2005-10-19 14:23 ` ebotcazou at gcc dot gnu dot org [this message]
2005-10-19 14:59 ` kargl at gcc dot gnu dot org
2005-10-19 15:09 ` ebotcazou at gcc dot gnu dot org
2005-10-19 17:34 ` kargl at gcc dot gnu dot org
2005-10-19 18:19 ` ebotcazou at gcc dot gnu dot org
2005-10-23 22:54 ` pinskia at gcc dot gnu dot org
2005-11-21 11:45 ` ebotcazou at gcc dot gnu dot org
2005-11-21 12:04 ` fxcoudert at gcc dot gnu dot org
2005-11-21 14:06 ` ebotcazou at gcc dot gnu dot org
2005-11-21 20:52 ` ebotcazou at gcc dot gnu dot org
2005-11-21 20:53 ` ebotcazou at gcc dot gnu dot 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=20051019142308.3838.qmail@sourceware.org \
    --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: 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).