From: Ron Chen <ron_chen_123@yahoo.com>
To: aslam@lanl.gov, gcc@gnu.org, Beowulf <beowulf@beowulf.org>
Cc: open64-devel@lists.sourceforge.net
Subject: RE: GCC/Fortran 90/95 questions
Date: Fri, 30 Nov 2001 19:56:00 -0000 [thread overview]
Message-ID: <20011201035522.85826.qmail@web14706.mail.yahoo.com> (raw)
Message-ID: <20011130195600.FjL8CEqJixdvAtQBzalnP3IJcKQ5y_rLuD4Y54fLl6k@z> (raw)
> 2) Does gcc support f90 or f95? If not is there any
> GNU compiler that does, are any expected to be in
> the future?
There is a compiler called open64, which is SGI's
compiler for IA64. They have a C front-end, which is
based on gcc, and they have another for f90. (I don't
know the details...)
Recently, they have ported the f90 front-end and
run-time to other compiler back-ends. Please read the
note below for details.
http://open64.sourceforge.net/
http://sourceforge.net/tracker/?group_id=34861&atid=413342
-Ron
===========================================================
Porting open64 F90 front-end to Solaris
This patch ports the open64 Fortran90 compiler front
end to sparc_solaris platform. Specifically, it ports
these three executable programs: "mfef90", "ir_tools",
and "whirl2f". ANY OTHER COMPONENT OF OPEN64 IS NOT IN
THE SCOPE OF THIS PATCH.
Tested platforms include sparc_solaris, mips_irix and
ia32_linux, using both GNU gcc and vendor compiler.
Makefiles, some header files and some c/c++ source
files were modified for porting.
__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com
next reply other threads:[~2001-11-30 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 18:27 Ron Chen [this message]
2001-11-30 19:56 ` Ron Chen
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 14:50 Steven Bosscher
2001-11-30 11:28 ` Steven Bosscher
2001-11-23 4:04 Tariq D. Aslam
2001-11-24 7:44 ` Andrea 'Fyre Wyzard' Bocci
2001-11-30 16:57 ` Andrea 'Fyre Wyzard' Bocci
2001-11-30 9:35 ` Tariq D. Aslam
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=20011201035522.85826.qmail@web14706.mail.yahoo.com \
--to=ron_chen_123@yahoo.com \
--cc=aslam@lanl.gov \
--cc=beowulf@beowulf.org \
--cc=gcc@gnu.org \
--cc=open64-devel@lists.sourceforge.net \
/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).