From: Brian Gough <bjg@network-theory.co.uk>
To: Achim Gaedke <achim@zpr.uni-koeln.de>
Cc: gsl discussion list <gsl-discuss@sources.redhat.com>
Subject: Re: trouble with bessel function test ...
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15124.2428.796624.988234@debian> (raw)
In-Reply-To: <Pine.GSO.3.95.1010529165820.9996C-100000@Octopussy>
Achim Gaedke writes:
> I ran specfunc/test in gdb:
>
> PASS: gsl_sf_bessel_Jnu_e(0.0001, 1.0, &r)
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xa6058 in gsl_sf_bessel_JY_steed_CF2 (nu=0.0001, x=0.10000000000000001,
> P=0xffbef428, Q=0xffbef420)
> at bessel.c:628
> 628 double den = br*br + bi*bi;
>
> Maybe, this way of initialisation is not possible in pic code...
> The gcc version was 2.8.0.
It's valid C ... beyond that I don't know what's causing it.
> I've tested it with egcs-1.1.2, there was no error in specfunc, but a
> compile error at
> /zpr/gcc/egcs1.1.2/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -g
> -O2 -c test.c
> /usr/ccs/bin/as: "/var/tmp/ccaQ2xka.s", line 2207: error: statement syntax
> /usr/ccs/bin/as: "/var/tmp/ccaQ2xka.s", line 2343: error: statement syntax
>
> maybe there is a problem with egcs...
I think so ... GSL won't be responsible for problems in .s files, that
is a compiler bug.
> With linux, I tried to build gsl-0.8 in a seperate build tree, but failed.
> Has anyone tried too?
It works fine for me. What error do you get? (and is it compiler
related?).
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Achim Gaedke
2001-12-19 13:20 ` Brian Gough [this message]
2001-12-19 13:20 ` Achim Gaedke
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Achim Gaedke
2001-12-19 13:20 Rodney Sparapani
2001-12-19 13:20 ` Brian Gough
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=15124.2428.796624.988234@debian \
--to=bjg@network-theory.co.uk \
--cc=achim@zpr.uni-koeln.de \
--cc=gsl-discuss@sources.redhat.com \
/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).