From: Craig Burley <burley@gnu.org>
To: oliva@dcc.unicamp.br
Cc: egcs@cygnus.com
Subject: Re: Results for egcs-2.91.42 19980621 (gcc2 ss-980502 experimental) testsuite on sparc-sun-sunos4.1.3
Date: Wed, 24 Jun 1998 10:08:00 -0000 [thread overview]
Message-ID: <199806241515.LAA11786@melange.gnu.org> (raw)
In-Reply-To: <199806240212.XAA20826@araguaia.dcc.unicamp.br>
>FAIL: g77.f-torture/execute/cabs.f execution, -O0
>FAIL: g77.f-torture/execute/cabs.f execution, -O1
>FAIL: g77.f-torture/execute/cabs.f execution, -O2
>FAIL: g77.f-torture/execute/cabs.f execution, -O2 -fomit-frame-pointer -finline-functions
>FAIL: g77.f-torture/execute/cabs.f execution, -Os
Could somebody with a SunOS 4.1.3 (or 4.1.x, I guess) system look
into this?
In particular, I wonder if this is a case of the wrong c_abs, z_abs,
or f__cabs being linked in (e.g. from a non-libf2c/libg2c library)?
We had that problem come up years ago during g77 alpha-testing, IIRC
on this same machine. I think Kate Hedstrom ran into that, and it
was basically due to not linking the libraries in the right order.
(And, now that I've changed some naming and placement of the libf2c
library...maybe the problem has resurfaced?)
tq vm, (burley)
next prev parent reply other threads:[~1998-06-24 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-23 22:55 Alexandre Oliva
1998-06-24 10:08 ` Craig Burley [this message]
1998-06-24 14:50 ` Alexandre Oliva
1998-06-24 20:08 ` Jeffrey A Law
1998-06-25 6:50 ` Fred Fish
1998-06-24 21:23 ` Craig Burley
1998-06-25 6:50 ` Dave Love
1998-06-26 7:16 ` Alexandre Oliva
1998-06-26 13:03 ` Craig Burley
1998-06-27 19:07 ` Alexandre Oliva
1998-06-27 22:14 ` Jeffrey A Law
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=199806241515.LAA11786@melange.gnu.org \
--to=burley@gnu.org \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/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).