From: Jakub Jelinek <jakub@redhat.com>
To: Brad Lucier <lucier@math.purdue.edu>
Cc: toon@moene.indiv.nluug.nl, gcc@gcc.gnu.org, staff@math.purdue.edu
Subject: Re: f77 correctness on Sparc
Date: Wed, 13 Sep 2000 14:02:00 -0000 [thread overview]
Message-ID: <20000913230700.N491@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200009132026.PAA07824@polya.math.purdue.edu>
On Wed, Sep 13, 2000 at 03:26:49PM -0500, Brad Lucier wrote:
> Toon:
>
> There are a large number of test failures and untested test cases in the
> current CVS f77 when compiled with -m64 -mcpu=ultrasparc on an Ultra 10
> running Solaris 2.8, see
>
> http://gcc.gnu.org/ml/gcc-testresults/2000-09/msg00114.html
>
> Is this a general 64bit problem, or are there specific problems with
> the sparc port?
If you want to use -m64 on sparc for anything math related, you need
SUBREG_BYTE patches, which are not yet integrated into CVS.
Jakub
next prev parent reply other threads:[~2000-09-13 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 13:27 Brad Lucier
2000-09-13 14:02 ` Jakub Jelinek [this message]
2000-09-13 14:09 ` Toon Moene
2000-09-16 13:44 ` Brad Lucier
2000-09-17 14:18 ` Toon Moene
2000-09-13 14:14 Brad Lucier
2000-09-18 11:59 Brad Lucier
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=20000913230700.N491@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=lucier@math.purdue.edu \
--cc=staff@math.purdue.edu \
--cc=toon@moene.indiv.nluug.nl \
/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).