public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41293] New: FGSL: Wrong code generated
Date: Mon, 07 Sep 2009 07:12:00 -0000 [thread overview]
Message-ID: <bug-41293-13404@http.gcc.gnu.org/bugzilla/> (raw)
This is with the Fortran bindings to the GNU Scientific Library,
http://www.lrz-muenchen.de/services/software/mathematik/gsl/fortran/
Compiling works OK, but the test suite shows a couple of failures with
gfortran:
Running montecarlo.exe:
FAIL: fgsl_monte_monte_vegas_getparams
FAIL: 1 of 21 tests failed
fgsl_monte_monte_vegas_getparams: aborting Execution
Running multimin.exe:
FAIL: fgsl_multimin_fdfminimizer_iterate
FAIL: 1 of 12 tests failed
Running error test:
OK: All 6 tests passed
FAIL: fgsl_interp_alloc:nofail
FAIL: 1 of 1 tests failed
The "multimin.exe" test might be a bug in the test suite as g95, ifort and
gfortran show the same error. (For g95 it is the only error, the ifort has
additionally for array.exe/poly.exe a segfault.)
--
Summary: FGSL: Wrong code generated
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41293
next reply other threads:[~2009-09-07 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 7:12 burnus at gcc dot gnu dot org [this message]
2009-09-07 10:29 ` [Bug fortran/41293] " burnus at gcc dot gnu dot org
2009-09-07 16:05 ` burnus at gcc dot gnu dot org
2009-09-07 16:25 ` burnus at gcc dot gnu dot org
2009-09-07 16:56 ` burnus at gcc dot gnu dot org
2010-01-08 9:49 ` burnus 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=bug-41293-13404@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: 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).