| segmentation error: SIGSEGV |
|
 |
Index ‹ fortran
|
- Previous
- 1
- Fortran Resources (April, 2004)*********************************************************************
Information file, on compilers, tools, books, courses, tutorials,
and the standard for the Fortran language and its derivatives.
This file can be viewed too at http://www.fortran.com/metcalf.htm
Additional information on Fortran is available at
http://www.fortran.com, http://www.fortranlib.com/ and
http://www.dmoz.org/Computers/Programming/Languages/Fortran/
You can join an active Fortran discussion group by going to
http://www.jiscmail.ac.uk/lists/comp-fortran-90.html.
*********************************************************************
WHAT'S NEW?
Since 19 February:
Add Watson's conversion scripts
Add a new link, above
Add FCAT, a coverage analysis tool.
Since 20 March:
None.
WHERE CAN I OBTAIN A FORTRAN 95 COMPILER?
Absoft offers source compatible F95 toolsets for Intel/AMD/Linux, PPC/Linux,
Macintosh OS9/OSX and Windows. These complete Fortran toolsets, called Pro
Fortran, include both F77 and F95 compilers plus complete a development
environment. All Absoft Pro Fortran toolsets provide full support for the
native environment, include graphics, precompiled math libraries, VAX/Unix
subroutine libraries, HDF libraries and free technical support. Software
Cluster Kits which include pre-configured MPICH, PVM, ScaLAPACK and PBS
are available for Linux systems. Auto parallelizing (SMP) and vectorizing
preprocessors, IMSL Math and Stat libraries are optional. Absoft also
distributes IBM's high-performance IBM XL Fortran compiler, v8.1,
for the G5/PowerMac running OSX: http://www.absoft.com.
Compaq offers highly optimizing Fortran 95 compilers for the following
platforms: Tru64 UNIX Alpha, OpenVMS Alpha, Windows 95/98/NT, and Linux
Alpha. The Windows product, Compaq Visual Fortran, includes the Microsoft
Developer Studio IDE which can be shared with Microsoft Visual C++.
Parallel execution using OpenMP-directed decomposition or HPF is included
on the Tru64 UNIX platform. On Windows NT, SMP parallel execution
using directed decomposition is available through Visual KAP.
Compaq Fortran for Linux Alpha Systems is available as a free
download under a Technology Enthusiast license for non-commercial use.
All Compaq Fortran 95 products include the Compaq Extended
Math Library of optimized scientific subroutines and the allocatable array
extensions. See: http://www.compaq.com/fortran or mail to
email***@***.com.
Cray has a fully-optimizing Fortran 95 compiler available for the
Cray PVP (J90, C90, T90, SV1), T3E, and X1 systems. The PVP compiler
supports automatic parallization and OpenMP. The T3E compiler
supports Co-Array Fortran. The X1 compiler supports automatic
streaming, OpenMP, Co-Array Fortran, and several Fortran 2003 features.
For more information on Co-Array Fortran see www.co-array.org.
The Fortran Company offers F, the subset language, for Unix and Windows,
some in highly optimizing versions. All of the full
professional versions of the F compiler are available free by downloading
them from the F anonymous ftp directory: ftp://ftp.swcp.com/pub/walt/F.
See also http://www.fortran.com and the book section below.
Fujitsu has a Fortran 95 compiler for the SPARC Solaris platform including
OpenMP 1.1 support. This SPARC Solaris compiler has been optimised for the
Fujitsu PRIMEPOWER systems:
http://www.fr.fse.fujitsu.com/devuk/solaris.shtml.
Fujitsu also has a Fortran 95 compiler for Linux (see
http://www.fr.fse.fujitsu.com/devuk/linux.shtml), and a highly optimized,
native Fortran 95 compiler, Fortran/VPP and HPF, for its VPP supercomputers.
Contact: email***@***.com.
Hewlett-Packard provides Fortran 95 compilers for the HP-UX operating system
running on PA-RISC and Itanium2 architectures. Release v2.6 currently
supports
the Fortran 95 language and OpenMP v2.0. See http://www.hp.com/go/hpfortran.
IBM XL Fortran for AIX, Linux and soon MAC OS X supports Fortran 95. XLF is
a highly optimized, native compiler designed to exploit the RS/6000
symmetric multi-processing (SMP) architecture as well as providing
support for 64-bit pointers and addressability for serial and SMP codes.
XLF V8.1 provides full support for the OpenMP Fortran API 2.0, allows
direct manipulation of the floating-point status and control register,
and provides a technical preview of the new IBM Distributed Debugger.
It also supports some features of Fortran 2000: allocatable components,
IEEE Floating Point Exception Handling, etc.
For more information: http://www.software.ibm.com/ad/fortran.
Intel produces a Fortran 95 optimizing compiler for Windows NT/2000/98/95
and linux that comes complete with its own debugger, module analyzer, and
preprocessor. The compiler performs automatic
vectorization, and takes full advantage of Intel's MMX and SSE instruction
extensions for the Pentium IV. It requires that Microsoft Visual C/C++
be installed (not on linux), and is capable of plugging into
Visual Studio. ifort for linux is available gratis for non-commercial use.
See http://www.intel.com/software/products/compilers/.
Lahey/Fujitsu Fortran 95 is produced by the Lahey/Fujitsu alliance. LF95
is available in three Windows configurations: Express, Standard, and
PRO, and two Linux configurations: Express and PRO. All configurations
feature: VAX, IBM, and POSIX language extensions, allocatable array
enhancements, etc. The Windows and Linux Express version is command-line
only and features the compiler, linker and debugger. PRO for Windows
adds a Fortran-smart Windows editor, a debugger, an AUTOMAKE make
utility, and an enhanced Winteracter Starter kit (WiSK) for creating
true Windows programs with Fortran, and a Coverage Analysis Tool that
detects unexecuted code and performs range of operation checking. The
PRO is compatible with Visual C++, Visual Basic, and Delphi and also
includes Fujitsu's SSL2 Math Library and Visual Analyzer (see below).
The PRO Linux version offers auto-parallelization, OpenMP compatibility,
thread-safe BLAS and LAPACK, WiSK, AUTOMAKE, and Fujitsu's SSL2. All
products come with free technical support and are available at
www.lahey.com. Also available is a subset compiler, elf90.
NAG provides a f95 compiler for most unix platforms (including Mac OS X and
Linux on x86 and Alpha), also for VMS and Microsoft Windows.
This was the first f9x compiler, in 1991. It supports the ISO extensions for
floating-point exception handling and allocatable array enhancements and
some F2003 extensions. The NAGWare f90 Tools are a suite of Fortran 90
tools that, among other things, perform F77 to f90 conversion. Contact
email***@***.com, email***@***.com, http://www.nag.co.uk/, or
http://www.nag.co.uk/nagware/NP/NP50_announcement.asp.
NA Software supplies Fortran 95 on PCs including Windows 95, NT and
Linux/x86. It includes the ISO extensions for IEEE arithmetic and
allocatable array enhancements, a native implementation of
ISO_VARYING_STRING, and a built-in module providing OpenGL conformance.
It also comes with a GUI-based source level debugger. A cheap student
version accepts files up to 2000 lines.
(http://www.nasoftware.co.uk/home.html).
NEC has a native, optimizing Fortran 95 compiler, FORTRAN90/SX,
with an automatic vectorization and parallelization capability, for its
supercomputer SX series. HPF/SX V2 provides functions conforming
to the specification of HPF1.1 and HPF2.0 and can be used with
vector processing functions in SX Fortran and with parallel processing
functions using microtasking. (email***@***.com).
Pathscale is bringing a high performance Fortran95 compiler for
Linux/Opteron and Linux/x86 to market. A beta version for Opteron begins in
January 2004, and general availability is scheduled for March. To sign
up for the beta, or for more details, see
http://pathscale.com/products1.html.
Salford Software markets FTN95, a Fortran 95 compiler for Win32, running
on Windows 95/NT/2000/XP PCs. It has announced its Fortran 95
compiler for Microsoft .NET (FTN95 for .NET). This compiler will produce
fast executables from source files that may be any combination of
Fortran 77, Fortran 90 and Fortran 95. FTN95 for .NET,
including integrated Help and Debugger, is supplied bundled with
FTN95 for Win32 and, optionally, with Microsoft Visual Studio for .NET.
A low-cost, fully-featured personal edition is also available:
email***@***.com or http://www.salfordsoftware.co.uk.
SGI has the MIPSpro Fortran 95 compiler (which now uses the Cray front
end) available for all SGI IRIX systems. It can be configured with an
optional Auto Parallelizing Option (APO) product to do automatic
parallelization of Fortran code. It supports OpenMP. See
http://www.sgi.com/software/irix/tools/fortran.html.
Sun has released a Fortran 95 compliant compiler as part of two
products: Sun ONE Studio 7, Compiler Collection and Sun ONE Studio 7,
Enterprise Edition for Solaris. The first of these products contains
command line-based (CLI) tools such as a compiler, building utility,
debugger, and the Sun Performance Library. The second product adds a
complete Integrated Development Environment (IDE) with GUI debugger,
performance tools, along with other components. Both have Interval
Arithmetic and are Open MP and MPI compliant. Improvements include
support for the upcoming Fortran 2000 standard with support for DECIMAL,
IOMSG, ROUND, and IEEE. Global program checking (GPC) has been
extended to perform static verification of OpenMP directives.
The software can be downloaded and be evaluated for free for 60 days at
http://wwws.sun.com/software/sundev/suncc/buy/index.html. For more
product information see
http://wwws.sun.com/software/sundev/index.html.
OTHER USEFUL PRODUCTS
Apogee's f90 compiler is highly optimized for SPARC architectures
(email***@***.com or http://www.apogee.com).
PGI has a Fortran 90/HPF compiler for SGI, IBM SP2, HP/Convex, and
Sun Ultra, as well as a native F90/HPF compiler for Intel-based
Linux/Solaris86/NT workstations and servers. The latter supports
auto-parallelization, native OpenMP parallelization, and HPF
parallelization (email***@***.com or http://www.pgroup.com).
MTASK, a high performance library for parallel computing with CVF and
other compilers is available free from www.equation.com
(from the "Fortran Supercomputing" menu select Download-Library).
A manual at: ftp://ftp.equation.com/mtask/document/mtask.pdf.
A Fortran-aware debugger is TotalView from Etnus, http://www.etnus.com/.
A fairly simple point and click style editor called jedit (java editor)
which has a Fortran support package is available at http://www.jedit.org/.
SofTek Systems, Inc. is a provider of a wide variety of HPF compilers,
tools, and technical expertise. See either email***@***.com or
http://www.softek.co.jp. Tel: 81-3-3412-6008, fax: 81-3-3412-7990.
Crescent Bay Software supplies VAST/77to90, an advanced Fortran 77 to
Fortran 90 converter. Products for auto-vectorization, auto-parallelization
and graphical profiling/tuning are also available. See
http://www.crescentbaysoftware.com/.
Intel's VTune Performance Analyzer increases software performance by
quickly analyzing all the files running on a CPU, including drivers, the
kernel, and the application, graphically showing what's spending the most
time in the CPU, and allowing one to "drill down" through processes,
threads, functions, etc. to the source files, identifying the bottlenecks in
the code: http://www.intel.com/software/products/vtune/vtune60/.
DMS Reengineering Toolkit is used for automated analyses and
changes to large software systems. This toolkit can parse large
systems of F77/F90/F95 and produce compiler-like abstract syntax
trees, etc. (http://www.semdesigns.com/Products/DMS/DMSToolkit.html).
Fujitsu Visual Analyzer (www.lahey.com): Visually
analyze the call structure and logic flow of your Fortran and Csource
code. Display a detailed cross reference of all the variables in the
program and where modules and commons are defined and referenced. Show
C global variable definitions and references as well. VA can help you
understand someone else's code, detect subtle programming errors across
multiple files, and verify compliance with the Fortran 95 standard.
FORCHECK is a static analyzer for Fortran programs. It analyses both the
individual program units and the whole program. It optionally verifies the
syntax for conformance to the Fortran 95 standard, and provides warnings
on undefined and unreferenced syntax items, inconsistent argument lists,
and much more. FORCHECK generates documentation, such as cross-reference
tables. See http://www.forcheck.nl.
FORESYS (FORtran Engineering SYStem) is an integrated set of tools
designed for engineers in charge of developing, maintaining and upgrading
programs written in Fortran. It is suited for, among other things,
migrating applications from Fortran 77 to Fortran 90. See Simulog below.
Fortran90-lint, for Fortran 90 program analysis, also other tools, from
http://www.cleanscape.net/products/downloads/ftpflint.html.
FCAT, a coverage analysis tool for F90/95 code, written in Perl, is at
http://www.dl.ac.uk/TCSC/UKHEC/FCAT/index.html .
Spackman & Hendrickson, Inc. supply SHAPE95, a comprehensive set of
Fortran 95 compiler conformance tests. There are over 7500 individual,
executable, self-checking, test subroutines. Each subroutine tests a
particular aspect of compiler conformance to the Fortran 95 standard.
The test suite is platform and OS independent and is bootstrapable from
a Fortran 90 compiler. Installation and training are also available.
For more information contact Dick Hendrickson, email***@***.com
(612) 378-9694.
MATFOR is a set of numerical and graphical libraries for Fortran
programmers in scientific and engineering fields (www.ancad.com).
Bradly Associates supplies the GINO and GINOMENU range of GUI and
Graphics libraries for Win32, Unix and OpenVMS with an F90 binding.
More information at www.bradassoc.co.uk.
A 2- and 3-D OpenGL graphics interface, f90gl, for Unix and Windows 95/NT,
is obtainable at http://math.nist.gov/f90gl. Latest version is 1.2. A
version
compatible with Lahey/Fujitsu Fortran 95 (LF95) and Lahey Fortran 90 (LF90)
is available at www.lahey.com/support/SetupF90gl.exe.
SansGUI, a modeling and simulation environment for incorporating a
graphical schematic model editor, graphical user interface, dynamic
charting, and animated OpenGL 3D graphics programming, all without the
need to write any GUI code, supports Compaq Visual Fortran on Windows
platforms. For product information, visit
http://www.protodesign-inc.com/sansgui.htm.
I.S.S. supplies Winteracter, a Fortran 9x GUI toolkit, providing
source-level compatibility between Win32 and Linux. See
http://www.winteracter.com.
HPF is available not only as listed above, but also on the definitive
list of sites to be found at www.ac.upc.es/HPFSurvey. See also
http://www.crpc.rice.edu/HPFF.
A source form convertor, convert.f90, is obtainable by ftp from
ftp.numerical.rl.ac.uk in the directory /pub/MandR. Latest version is 1.5.
Another is Alan Miller's to_f90.f90 at http://users.bigpond.net.au/amiller/.
Layne T. Watson has sed and perl scripts in a package to correct
obsolete and unsupported FORTRAN constructs for use with standard
Fortran 90: http://people.cs.vt.edu/~ltw/f77tof90/.
A free set of wrapper routines to call a subset of Xlib routines from
Fortran 90 is available from Garnatz and Grovender, Inc.:
email***@***.com, http://www.winternet.com/~gginc/, or
ftp.winternet.com/users/gginc.
NAG (see above) and IMSL (now Visual Numerics, email***@***.com)
offer f90 versions of their maths libraries that take full advantage of
the language's library building capabilities.
An f90 mode is included in the official Emacs distribution (GNU
Emacs-19.28/XEmacs-19.13 or later).
For make files, a perl5 script, which behaves like an X11 makedepend
program (it edits an existing Makefile) and recursively searches
include files for more dependencies, is available from Kate Hedstrom:
ftp://ahab.rutgers.edu/pub/perl/sfmakedepend
http://marine.rutgers.edu/po/perl.html
For a makemake perl script: http://www.fortran.com/fortran/makemake.html.
Another f90-aware Makefile maker written in perl is available
at http://www.gfdl.gov/~vb/mkmf.html.
Yet another makedepf90 program is available (free) at
http://www.helsinki.fi/~eedelman/makedepf90.html.
Polyhedron Software's plusFORT Version 6.0 has comprehensive facilities
for translation of Fortran 77 and VAX Fortran to Fortran 90. A new
Windows front-end is available for the NT version. A major feature is
AUTOMAKE, which automatically detects Fortran 90 module dependencies.
email***@***.com, http://www.polyhedron.com/.
A F90 source for a f90split utility is at
ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/f90split.f90.gz. See also
http://www.ifremer.fr/ditigo/molagnon/fortran90/ and
ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/moware-1.0.tar.gz to get an
F90 to PostScript list program and an F90 aware pre-processor similar to
cpp, but with pretty-printing for the pre-processed code.
A C2F.ZIP file is available at http://home.cfl.rr.com/davegemini/C2F.ZIP.
It contains C2F.EXE, a C->F90 "hands-off" translator program for Win95/NT.
Some coding and style guidelines have been developed by the European
meteorologists:
www.meto.gov.uk/research/nwp/numerical/fortran90/f90_standards.html.
f90SQL offers a convenient and familiar way to directly read and
write data from your Fortran programs to many applications formats.
See info about the library at http://www.canaimasoft.com/f90sql.
HicEst is a small programming tool with integrated editor, incremental
compiler, interpreter and debugger designed for immediate results during
development of technical or scientific applications. It can also be used as
a Windows GUI wrapper to call existing code in a DLL. See
http://www.HicEst.com.
WHAT BOOKS ARE AVAILABLE?
English books on Fortran 95:
Compaq Visual Fortran: A Guide to Creating Windows Applications
- Norman Lawrence, Digital Press (an imprint of Butterworth-Heinemann)
2001, ISBN 1-55558-249-4.
Fortran 90/95 Explained (2nd. edition) - Metcalf & Reid, Oxford U.
Press, 1999, ISBN 0-19-850558-2, about $33. This book is a complete,
audited description of the Fortran 90 and Fortran 95 languages in a
more readable style than the standards themselves. It incorporates
all J3 and WG5's interpretations and has chapters on the floating-point
exception handling and the data type enhancement of the official ISO
extensions. It has six Appendices, including an extended example program
that is available by ftp and solutions to exercises. For US orders:
www.oup-usa.org or toll free 1-800-451-7556; in the UK: www.oup.co.uk.
An electronic version is available at www.books24x7.com.
Fortran 90/95 for Scientists and Engineers, 2nd ed., McGraw Hill, S. J.
Chapman, 2004, ISBN 0-07-282575-8.
Fortran 95 - Counihan, UCL, 1997, 185728367-8.
Fortran 95 Handbook - Adams, Brainerd, Martin, Smith and Wagener,
MIT, 1997, ISBN 0-262-51096-0.
Fortran 95 Language Guide - Gehrke, Springer, London, 1996,
ISBN 3-540-76062-8.
Fortran Top 90--90 Key Features of Fortran 90, Adams, Brainerd,
Martin, Smith. Unicomp, 1994, ISBN 0-9640135-0-9
Introducing Fortran 95 - Chivers and Sleightholme , Springer Verlag,
London.
Introduction to Fortran 90/95 - Chapman, McGraw-Hill, 1997, ISBN
0-07-011969-4.
Introduction to Fortran 90/95, Algorithms, and Structured Programming,
Part 1: Introduction to Fortran 90, Part 2: Algorithms and Fortran 90.
R. Vowels: 93 Park Drive, Parkville 3052, Victoria, Australia,
(email***@***.com). $43 Aust with disk, ISBN 0-9596384-8-2.
Object Oriented Programming via Fortran 90/95 - Ed Akin, Cambridge
University Press, 2003, ISBN 0-521-52408-3.
Programming in Fortran 90/95 -- Morgan & Schonfelder, available in
Acrobat PDF format from www.fortran.com or www.nasoftware.co.uk.
The DIGITAL Visual Fortran Programmer's Guide, ISBN 1-55558-218-4,
April, 1999.
English books on Fortran 90:
Fortran 90 - Meissner, PWS Kent, Boston, 1995, ISBN 0-534-93372-6.
Fortran 90 - Huddleston, Exchange Publ. Div., Buffalo, NY, 1996,
ISBN 0-945261-07-1.
Fortran 90 and Engineering Computation - Schick and Silverman, John
Wiley, 1994, ISBN 0-471-58512-2.
Fortran 90 Concise Reference - Wagener, Absoft, 1998,
ISBN 0-9670066-0-0.
Fortran 90 for Engineers - Etter, Benjamin/Cummings, Redwood City,
1995, ISBN 0-201544-46-6.
Fortran 90 for Engineers and Scientists - Nyhoff and Leestma,
Prentice Hall, 1996, ISBN 0-13-519729-5. An 'Introduction to ....'
also exists: 1996, ISBN 0-13-505215-7.
Fortran 90 for Scientists and Engineers - Brian D. Hahn, Edward
Arnold, 1994, ISBN 0-340-60034-9.
Fortran 90 Programming - Ellis, Philips, Lahey, Addison Wesley,
Wokingham, 1994, ISBN 0-201-54446-6.
Problem solving with Fortran 90: for scientists and engineers -
Brooks, 1997, Springer, 0-387-98229-9.
Programmer's Guide to Fortran 90, third edition - Brainerd, Goldberg
and Adams, Springer, 1996, ISBN 0-387-94570-9.
Programming in Fortran 90 - I.M. Smith, Wiley, ISBN 0471-94185-9.
Upgrading to Fortran 90 - Redwine, Springer-Verlag, New York, 1995,
ISBN 0-387-97995-6.
English books on subset languages:
Algorithms and Data Structures in F and Fortran - Vowels, Unicomp,
1998, ISBN 0-9640135-4-1. Order from http://www.fortran.com.
essential Fortran 90 and 95 - Meissner, Unicomp, 1997,
ISBN 0-9640135-3-3.
Key Features of F - Adams, Brainerd, Martin and Smith, 1996, ISBN
0-9640135-2-5, Unicomp.
Programmer's Guide to F - Brainerd, Goldberg and Adams, 1996, ISBN
0-9640135-1-7, Unicomp.
The F Language Guide - Gehrke, Springer, London, 1997,
ISBN 3-540-7615-9.
The F Programming Language - Metcalf and Reid, Oxford University Press,
1996, ISBN 0-19-850026-2, about $33. This book is the definitive
description of the F programming language - a carefully crafted subset
of Fortran 90 that is highly regular and stripped of Fortran's older,
dangerous features, but retains the powerful array language, data
abstraction and pointers. It has six Appendices, including an extended
example program that is available by ftp and solutions to exercises.
Orders: www.oup-usa.org or toll free 1-800-451-7556; UK: www.oup.co.uk.
English books on related topics:
Advanced Scientific Computing - Wille, Wiley, 1995, ISBN 0471-95383-0.
Atlas for Computing Mathematical Functions ... in Fortran 90 and
Mathematica - Thompson, Wiley, 1997, 0-471-18171-4.
Contemporary Computing for Technical Engineers and Scientists: using
Fortran 90 and spreadsheets - Forsythe, PWS, 1997, 0-534-93139-1.
Numerical Recipes in Fortran 90: The Art of Parallel Scientific
Computing, Volume 2 of Fortran Numerical Recipes - Press, Teukolsky,
Vetterling and Flannery, Cambridge U. Press, ISBN 0-521-57439-0, 1996.
Code can be downloaded (purchased) from http://www.nr.com.
A CDROM is also available (see Web site).
Chinese:
Programming Language Fortran 90 - He Xingui, Xu Zuyuan, Wu Qingbao and
Chen Mingyuan, China Railway Publishing House, Beijing,
ISBN 7-113-01788-6/TP.187, 1994.
Fortran 90 - Walter S. Brainerd, Charles H. Goldberg, Jeanne C. Adams,
CHEP, Beijing and Springer, Berlin, 2000, ISBN 7-04-007937-2
(a translation of Programmer's Guide to Fortran 90).
Dutch:
Fortran 90 - W.S. Brainerd, Ch.H. Goldberg, and J.C. Adams, translated
by J.M. den Haan, Academic Service, 1991, ISBN 90 6233 722 8.
Finnish:
Fortran 90 - Haataja, Rahola and Ruokolainen, Center for Scientific
Computing (Finland), 1996, 286 pages, ISBN 952-9821-33-6.
WWW version: http://www.csc.fi/oppaat/f90/
French:
Fortran 90; Approche par la Pratique - P. Lignelet, S閞ie
Informatique 蒬itions, Menton, 1993, ISBN 2-909615-01-4.
Fortran 90. Les concepts fondamentaux, the translation of "Fortran
90 Explained" M. Metcalf, J. Reid, translated by M. Caillat and
B. Pichon, AFNOR, 1993, Paris, ISBN 2-12-486513-7.
Fortran 90; Initiation ?partir du Fortran 77 - Aberti, S閞ie
Informatique 蒬itions, Menton, 1992, ISBN 2-909615-00-6.
Les sp閏ificit閟 du Fortran 90, M. Dubesset et J. Vignes,
蒬itions Technip, 1993. ISBN 2-7108-0652-5.
Manuel complet du langage Fortran 90, et guide d抋pplication,
P. Lignelet, S閞ie Informatique 蒬itions, 1995. ISBN 2-909615-02-2.
Manuel Complet du Langage Fortran 90 et Fortran 95, Calcul
intensif et G閚ie Logiciel, P. Lignelet, Masson 蒬itions,
Paris, 1996, ISBN: 2-225-85229-4.
Programmer en Fortran 90, C. Delannoy, Eyrolles, 1992,
ISBN 2-212-08723-3.
Traitement des donn閑s num閞iques avec Fortran 90, M. Olagnon,
Masson 蒬itions, 1996, ISBN 2-225-85259-6.
Structures des donn閑s (et leurs algorithmes) en Fortran 90/95,
P. Lignelet, Masson 蒬itions, Paris, ISBN 2-225-85373-8.
German:
Fortran 90 Lehrbuch - D. Rabenstein, Hanser, 1995, ISBN 3-446-18235-7.
Die Programmiersprache F - W. Gehrke, Springer-Verlag, ISBN 3-540-63376-6.
Fortran 90 - B.Wojcieszynski and R.Wojcieszynski, Addison-Wesley, 1993,
ISBN 3-89319-600-5.
Fortran 90: eine informelle Einf黨rung - M. Heisterkamp,
BI-Wissenschaftsverlag, 1991, ISBN 3-411-15321-0.
Fortran 90 Kurs: technisch orientiert - G. Schmitt, Oldenbourg,
1996, ISBN 3-486-23896-5.
Fortran 90, Lehr- und Arbeitsbuch f黵 das erfolgreiche Programmieren -
W.S. Brainerd, C.H. Goldberg, and J.C. Adams, translated by P. Thomas
and K. Paul, R. Olbenbourg Verlag, Muenchen, 1994, ISBN 3-486-22102-7.
Fortran 90 Lehr- und Handbuch - T. Michel, BI-Wissenschaftsverlag, 1994.
Fortran 90 Referenz-Handbuch: der neue Fortran-Standard - W. Gehrke,
Carl Hansen Verlag, 1991, ISBN 3-446-16321-2.
Programmierung in Fortran 90 - Schobert, Oldenburg, 1991.
Programmierung mit Fortran 90 - B鋟mer, Vieweg, Braunschweig, 1997,
ISBN 3-528-05208-2.
Programmieren in Fortran - Erasmus Langer, Springer-Verlag, Wien,
New York, 1993. ISBN 3-211-82446-4, 0-387-82446-4.
Software Entwicklung in Fortran 90 - 躡erhuber and Meditz, Springer
Verlag, 1993, ISBN 0-387-82450-2.
Italian:
Some resources in Italian, including a manual, are at
http://space.tin.it/computer/gciabu.
Japanese:
Fortran 90 Explained - Metcalf and Reid, translated by H. Nisimura,
H. Wada, K. Nishimura, M. Takata, Kyoritsu Shuppan Co., Ltd., 1993,
ISSN 0385-6984.
Russian
An Explanation of the Fortran 90 Programming Language (translation of
Fortran 90 Explained - Metcalf and Reid), translated P. Gorbounov,
Mir, Moscow, 1995, ISBN 5-03-001426-8. Available also from
email***@***.com.
FORTRAN 77 to Fortran 90 Tutorial - Einarsson and Shokin, Russian
Academy of Sciences, Novosibirsk, 1995, ISBN 5-85826-013-6.
Swedish
Fortran 90 - en introduktion - Blom, Studentlitteratur, Lund, 1994,
ISBN 91-44-47881-X.
WHERE CAN I OBTAIN COURSES, COURSE MATERIAL OR CONSULTANCY?
Copyright but freely available course material is available
on the World Wide Web from the URLs:
Paul Dubois's lecture notes and class materials on "Object Based
Programming in Fortran 90" at
http://prdownloads.sourceforge.net/pyfortran/OBF90.zip. (In WinZip,
on the Options|Configuration menu, turn off "tar smart convert CR/LF".)
Manchester Computer Centre:
http://www.hpctec.mcc.ac.uk/hpctec/courses/Fortran90/F90course.html
or via ftp: ftp.mcc.ac.uk, in the directory /pub/mantec/Fortran90.
U. of Liverpool: http://www.liv.ac.uk/HPC/HPCpage.html - covers
f90 and HPF, with Java-enhanced Web pages.
CERN: http://wwwinfo.cern.ch/asdoc/f90.html.
In French: Support de cours Fortran 90 IDRIS - Corde & Delouis (from
www.idris.fr/data/cours/lang/fortran/choix_doc.html).
U. of Edinburgh (on HPF): http://
www.epcc.ed.ac.uk/epcc-tec/course-packages/HPF-Package-form.html
Linkoping U.: http://www.nsc.liu.se/f77to90.html.
Courses and conversion consultancy are available from:
Walt Brainerd, a former member of J3, also on HPF (email***@***.com).
Tom Lahey (email***@***.com).
PSR (see Veridian above).
PTR Associates, based in Wokingham, UK, offers a Fortran 95 course:
http://www.ptr.co.uk/fortran-programming.html.
Michael Metcalf, formerly of CERN, Switzerland, and an ex-member of
J3 and WG5, offers a Fortran 95 course that lasts for six 75-minute
sessions. There is an F version too. He is happy to negotiate holding
either version anywhere in the world. These courses are suitable for
graduates, or equivalent level, and are a useful way to 'kick-start'
a Fortran 90/95 or an F activity at a given site. Contact at
email***@***.com, or Manfred-von-Richthofen Strasse 15,
12101 Berlin, Germany, +0049.30.78952573.
John Reid, formerly of J3 and a member of WG5, offers a Fortran 90
course. He is happy to negotiate holding it anywhere in the world.
It is suitable for graduates, or equivalent level, and is a useful
way to 'kick-start' a Fortran 90 activity at a given site.
Contact email***@***.com.
Purple Sage Computing Solutions, Inc. is offering three Workshops
to Fortran programmers: The Fortran Modernization, Optimization
and Parallelization Workshop; The Parallelization for Fortran
Programmers Workshop; and The fthreads Workshop. Contact
email***@***.com or http://users.erols.com/dnagle. Also on offer
is a one day workshop on the new features of Fortran 2000. See
http://users.erols.com/dnagle/wsf2000.html for more details.
Cranfield University (Shrivenham Campus) offers a 5-day course
"Scientific Programming with Fortran 95", and by arrangement,
a 3-day course "Fortran 90 for Fortran 77 Programmers". Courses
can also be arranged on demand and tailored to requirements.
See http://www.rmcs.cranfield.ac.uk/amorg and follow link to
AMORG Short Courses.
Simulog, attn. Mr. E. Plestan,
1 rue James Joule, F-78286 Guyancourt Cedex, France
tel: +33 1 30 12 27 80 fax: +33 1 30 12 27 27
email***@***.com, http://www.simulog.fr
A Japanese company offering courses and conversion consultancy is:
SofTek Systems, Inc. (see above).
WHERE CAN I FIND THE FORTRAN AND HPF STANDARDS?
The Fortran 95 standard document is available from ISO, and replaces
Fortran 90. The document reference number is ISO/IEC 1539-1:1997. See
http://www.iso.ch, or contact
ISO Publications, 1 rue de Varembe, Case postale 56
CH-1211 Geneva 20, Switzerland
Fax. +41 22 734 10 79
It may also be obtained from national member bodies such as
ANSI, 1430 Broadway, New York, N.Y. 10018
in particular at its documentation store:
http://webstore.ansi.org/ansidocstore/find.asp?
The HPF 2.0 document is available as
ftp://softlib.rice.edu/pub/HPF/hpf-v20.ps.gz.
*****
This information is compiled on a 'best-effort' basis and is without
prejudice. It may be freely copied and disseminated. Corrections and
additions are solicited.
Mike Metcalf
(email***@***.com)
Version of 22 March, 2004.
- 1
- Ouuch!Bruce AKA email***@***.com wrote:
> Steve Layton writes:
>
> > Drew McManus posted a link to a short MP3 of "how NOT to end your
year"...
> > It's a concert performance of The Messiah, everything is going just
> > swimmingly, until the last "grand" chords...shudder...
>
> Although not quite as funny,
LOL!!! LOL!!! That's hysterical! LOL!!! Your a laugh a minute,
Bruce (AKA Tholen)!!!! You are SO fucking funny!!!!!
> I was masturbating at a performance of the Hallelujah
> Chorus during which the audience was invited to sing along.
Oh, stop it! I'm doubling over in hilarity, Bruce (AKA Tholen)!
> Right
> during the grand pause, some little girl was on autopilot and kept
> right on going with another "Hallelujah!" So much for the grand
pause.
I'll bet you bitched like the complete arsehole you are, Bruce (AKA
Tholen)!
302
- 1
- F95 and F77 compatabilityJust a quick query - we're going to be attempting to port a Fortran 77
application into a Windows application - it's been decided (by others)
that we're going to buy one of Salford Software's compilers to do it.
Our question is - is Fortran 95 backwardly compatible with Fortran 77,
and in any case, is there any particular advantage in purchasing
and using a Fortran 95 compiler over a Fortran 77 compiler?
Dave
- 2
- What is wrong with this search for the character PV/PQ program readcvcq
Implicit integer*2 (I-N)
character*8 C,'PV/PQ'
character*36 fn,fn1
character*8 cvocq (10)
parameter(fn='sxsoutfile')
parameter(fn1='dummy')
open (unit = 15, file=fn,status='old',access='sequential'
$ ,form='formatted')
open (unit = 16, file=fn1,status='old',access='sequential'
$ ,form='formatted')
do kount=1,1000
read (15,901,end=999) c,(cvocq(i),i=1,8)
c
c if (kount .gt. 163 .and. kount .lt. 170) write(16,902) c
c if (kount .gt. 163 .and. kount .lt. 170) write(6,*) kount
write (6,902) c,(cvocq(i), i=1,8)
if (c .eq. PV/PQ ) write (16,902) c,(cvocq(i), i=1,8)
enddo
c
901 format(a8,8a8)
902 format(1x,a8,8a8)
999 stop
- 5
- Components of derived types with pointer attributesHi,
I am having lots of troubles understanding how memory allocation works
and what the operator "=" means for certain derived data type
with components having pointer attributes.
Take the following routine:
========================================================================
PROGRAM main
IMPLICIT none
TYPE test
INTEGER :: illa
REAL(8), DIMENSION (:), POINTER :: s
END TYPE test
TYPE(test) :: a,b
INTEGER, SAVE :: m = 10000
ALLOCATE(a % s (m))
ALLOCATE(b % s (m))
a % s = 1.0D0
b % s = a % s
a % s ( 8) = 2.0D0
print*, a % s(8)
print*, b % s(8)
END PROGRAM main
========================================================================
The output of this program looks like:
2.00000000000000
1.00000000000000
If I replace the line
b % s = a % s
with
b = a
the output looks like:
2.00000000000000
2.00000000000000
Which seems to indicate that the statement "b = a" assigns the pointer
components in b to the addresses of a % s. Why this? What does the
standard f95 tell? I tried only with four implementations of f90/f95:
intel, pgi, g95 and compaq f90.
The code also works and gives the same result, if b % s is not
allocated. Which makes me wonder what happens to the memory allocated
in the example code by
ALLOCATE(b % s (m))
Memory leakage perhaps if I call a corresponding routine many times?
Any clues?
Thanks in advance
-- Massimo Marchi
-- Commissariat a l'Energie Atomique
-- DSV-DBJC-SBFM
-- Centre d'Etudes de saclay
-- Gif sur Yvette, FRANCE
- 7
- Intel ifort compiler problem - part IISteve Lionel wrote:
> On 10 Feb 2004 13:07:41 +0100, David Ham <email***@***.com> wrote:
>
>
>
>>>If one downloads the ifort compiler from scratch (I'm thinking
>>>of my customers here) do you get the latest build or do you have
>>>to apply the patches available on the Premier site. It's less than a
>>>week since I downloaded my new copy - has it really got up to 8.0.40
>>>already?
>>
>>Intel has a pretty rapid release cycle but they also don't use all the
>>numbers. I guess some of the intervening releases are only used
>>internally and don't make it to public release.
>
>
> That is correct.
>
> Customers who purchase a product with full support get access to the latest
> kit for download - we're not actually doing patches yet,, but that is coming.
>
> If you get the free, limited-support kit, that is not updated as frequently.
>
Steve,
Above and beyond the more-frequent updates which full support brings,
does Intel prioritize bugs submitted by full-support users over
limited-support users? I ask because I'm wondering whether purchasing
ifort for Linux will accelerate work on a showstopping (for me) bug
which I submitted last year (see support issue #220618).
cheers,
Rich T
- 9
- What sort of literal is this?Richard Maine wrote:
>
> Walter Spector <email***@***.com> wrote:
>
> > glen herrmannsfeldt wrote:
> > > .... If Hollerith constants in DATA statements
> > > didn't, then one wouldn't be able to compare DATA constants with
> > > A input, which would at least be a quality of implementation issue.
> >
> > Give the man a cigar!
>
> And I have *DEFINITELY* used systems where you couldn't compare such
> things. I forget the reason; might or might not have been this. It was a
> PITA.
That would be akin to having a different internal representation of
integer or floating point data based on whether it was read or DATA
initialized. Even code written to PFORT standards (1 char per NSU) would
break. I think most programmers would consider such a compiler
unusable.
Did they actually state that they were standards conforming?
W.
- 10
- max(NaN,0) should be NaNAfter tracking down a bug in my Fortran program, I found that it
assumed
max(NaN,0.) = 0.
This makes no sense, as the outcome of the operation is undefined and
should be NaN.
max(NaN,0.) = NaN
After researching, it appears the first outcome is accepted behavior,
and might be included in the revised IEEE 754 standard, which affects
not only Fortran. The discussion posted at
www.cs.berkeley.edu/~ejr/Projects/ieee754/meeting-minutes/02-11-21.html#minmax
suggests that "There is no mathematical reason to prefer one reason to
another."
But I think otherwise, for the following reason. Suppose the NaN is
produced by x/y, where x=0 came from an underflow and y=0 came from an
underflow. Then x/y would be a well-defined number that could be
postive or negative. The convetion max(NaN,0.) = 0. is wrong at least
half the time.
- 11
- OT: Survey : Measuring SoftwareThis survey addresses productivity tools and includes proposed support
for Fortran. My guess is that it likely refers to FORTRAN 77 support
(based on the way it seems to lump all "old" languages together), but I
made sure to include commentary defining the version of Fortran that any
such tools should support. I appear to not have acquired any virus or
worm from this site, but use at your own risk.
Kim Winslow wrote:
> Greetings!
>
> I am part of a small group of MBA students at Binghamton University
> conducting research on the use of productivity tools in the software
> industry for a school project. I'm writing to request about 5 minutes of
> your time to take a quick survey about software measurement by clicking
> on the link below. Your feedback is very valuable to us.
>
> We hope you can spare a few minutes of your time to help us with this
> school project. All responses are confidential and you can remain
> anonymous.
>
> Upon completion of the survey, you will be given access to a
> summarization of the results. This will let you see the trends of what
> other companies are doing when it comes to measuring software. Of
> course, individual responses remain confidential.
>
> Thank you!
>
> Here is the survey:
>
> http://www.zoomerang.com/survey.zgi?p=U26GGP6K4CY5
>
>
>
--
Gary Scott
mailto:garylscott@sbcglobal dot net
Fortran Library: http://www.fortranlib.com
Support the Original G95 Project: http://www.g95.org
-OR-
Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html
If you want to do the impossible, don't hire an expert because he knows
it can't be done.
-- Henry Ford
- 11
- Exchanging arrays in dll compiled with G95Dear all,
I succeeded in making a dll with G95 and calling it by VB5 (thanks to
Elliot suggestions). But now I've a new issue: I can't exchange arrays
between the two environments.
I made a simple fortran subroutine esempio.f90:
subroutine esempio(a,b)
double precision a(3),b(3)
b(1)=a(3)
b(2)=a(2)
b(3)=a(1)
open(unit=100,file="log.dat")
write(100,*) 'a: ',a(1),a(2),a(3)
write(100,*) 'b: ',b(1),b(2),b(3)
close(100)
return
end subroutine
compiled it with:
g95 -s -shared -mrtd -o esempio.dll esempio.def esempio.f90
where esempio.def is:
EXPORTS esempio=esempio_
and called it from VB5:
Private Declare Sub scambia Lib "esempio.dll" Alias "esempio" (x As
Double, y As Double)
Dim a(1 To 3), b(1 To 3) As Double
Private Sub Command1_Click()
a(1) = Text1
a(2) = Text2
a(3) = Text3
Call scambia(a(1), b(1))
Text4 = b(1)
Text5 = b(2)
Text6 = b(3)
End Sub
... after giving the array a the values [1 2 3].
After calling, the dll response has been:
a: 1. 0. 7.437354E-317
b: 7.437354E-317 0. 1.
that is: only the first value of the array a(1) has been passed to the
dll. Moreover, even if the values of a(2) and a(3) where wrong, the a
items inverted order has been correctly returned to VB5.
Could anyone give me some advice?
thanks in advance,
Walter
- 12
- GUIs with Dislin -more examplesHello
Although some examples are shown at http://www.star.le.ac.uk/~cgp/dislinGUI.html,
I wonder whether someone out there would have a couple of more
examples on how to make GUIs with dislin (fortran).
Right row, I need to know how to create a GUI where I can enter real*8
values on two separate columns, one next to the other (something like
an excel sheet). Each column should hold 24 values.
Any help would be most appreciated.
Many thanks
Ed
- 12
- Reference Information Manager (RIM) SourceI've searched high and low for the public domain source to RIM. This
was an F66/F77 based database manager. I find references that it is
public domain source, but can't locate the source (also searched Boeing,
NASA and U of Washington). Any pointers?
--
Gary Scott
mailto:garylscott@sbcglobal dot net
Fortran Library: http://www.fortranlib.com
Support the Original G95 Project: http://www.g95.org
-OR-
Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html
If you want to do the impossible, don't hire an expert because he knows
it can't be done.
-- Henry Ford
- 13
- Inquire StatementHi! All,
I am trying to check if a directory exists using the inquire
statement. On all systems I have tried so far (Linux RH 7... using PGF
& INTEL compilers, SGI, IBM P3 and P4, CRAY T3E) this seems to work,
i.e. using
inquire(file = dir, exist = fexist)
where dir is the directory name, returns true if a directory exist and
false otherwise. But on the Compaq, it returns false for a directory,
irrespective. Is the support for directories an extension or standard?
Is there any other way to check for directories, (pls. no shell
command solutions!)?
Thanks
ajs
- 15
- crossing a tree ?Hello list members,
first of all: thanks to the replys to my question about writing a tree !
Now I have the problem to cross my tree from the root to the most left
branch. My tree is an up to ternary tree. The branches are indicated by
the pointer -from the left to the right- r%next1, r%next2, r%next3
My suboutine is th following one:
RECURSIVE SUBROUTINE goto_end(r)
USE daten_test
TYPE(res), INTENT(IN), TARGET:: r
LOGICAL:: as4, as5, as6
INTEGER:: found
found = 0
as4 = ASSOCIATED(r%next1)
as5 = ASSOCIATED(r%next2)
as6 = ASSOCIATED(r%next3)
IF((as4.EQ.(.TRUE.)).AND.(found.EQ.0))THEN
CALL goto_end(r%next1)
found = 1
ENDIF
IF((as5.EQ.(.TRUE.)).AND.(found.EQ.0))THEN
CALL goto_end(r%next2)
found = 1
ENDIF
IF((as6.EQ.(.TRUE.)).AND.(found.EQ.0))THEN
CALL goto_end(r%next3)
ENDIF
END SUBROUTINE goto_end
This works fine, I reach the end, but then the subroutine does not stop
but goes upward again. But there are no pointers backward called r%next ...
By the way: I work with Microsoft Developper Studio 97.
Thanks for your help in advance !
Klemens
- 15
- linked lists Hi there,
I have a question, any help would be appreciated.
Can I have, in fortran90/95, linked lists of linked lists?
For example is it correct in Fortran90/95 statement as:
type L_1
character(1) :: ch
type (L_1) , pointer :: next
end type L_1
type L_2
type(L_1) :: one_word
type (L_2) , pointer :: next
end type L_2
type (L_2) the_sentence
I tried and it compiled, however I could not extract the quantities
the_sentence%one_word%ch, the_sentence%one_word%next%ch ,
the_sentence%one_word%next%next%ch ,..., which are supposed to be
character(1)
Thanks,
JD.
|
| Author |
Message |
snfinder@naver.com

|
Posted: 2006-9-25 13:55:29 |
Top |
fortran, segmentation error: SIGSEGV
I coded some integral cos(t^2) in [0,1] using trapzd.f90 subroutine.
It is compiled well, but segmentation error occurs when execute it.
Following text is output of idb.
error message:
******************** XXXXXXX ****************************
3 4 0.2173511732
4 8 1.0691014455
5 16 1.5692780733
6 32 0.1210473473
7 64 0.0412630614
8 128 0.0943264767
9 256 0.1164983573
10 512 0.1266963443
11 1024 0.1315937138
12 2048 0.1339942939
13 4096 0.1351828314
14 8192 0.1357742005
15 16384 0.1360691527
16 32768 0.1362163957
17 65536 0.1362902634
18 131072 0.1363288458
19 262144 0.1363479746
20 524288 0.1362782141
Program received signal SIGSEGV
trapzd (func=(function [0x0000000000000000]), a=6.95319085207303e-310,
b=<no value>, s=<no value>, n=<no value>) at trapzd.f90:22
22 fsum=sum(func(arth(a+0.5_dp*del,del,it)))
n=20 is critical point. It stop if n >20.
How can I fix it? I want to run to much large n.
I work on FC5 linux (64bit), intel xeon dual cpu machine using
ifort(intel fortran compiler 9.1)
Help me experts~~~
|
| |
|
| |
 |
Joost

|
Posted: 2006-9-25 14:13:00 |
Top |
fortran >> segmentation error: SIGSEGV
snfinder@naver.com wrote:
> 20 524288 0.1362782141
>
> Program received signal SIGSEGV
> trapzd (func=(function [0x0000000000000000]), a=6.95319085207303e-310,
> b=<no value>, s=<no value>, n=<no value>) at trapzd.f90:22
> 22 fsum=sum(func(arth(a+0.5_dp*del,del,it)))
>
> n=20 is critical point. It stop if n >20.
>
> How can I fix it? I want to run to much large n.
>
> I work on FC5 linux (64bit), intel xeon dual cpu machine using
> ifort(intel fortran compiler 9.1)
try setting the stack space much larger. depending on your shell
ulimit -s 128000
or something like this. You need to do that, basically, every time
before you run your application. Or you allocate explicitly a temporary
array for the argument in sum (just guessing).
Joost
|
| |
|
| |
 |
snfinder@naver.com

|
Posted: 2006-9-25 15:33:00 |
Top |
fortran >> segmentation error: SIGSEGV
Thank you Joost ^^
But I can't understand your saying. I'm not good at fortran and linux.
Can you explain it more details?
You mean it is not wrong of my code but shell setting problem?
PDS (-:
|
| |
|
| |
 |
Joost

|
Posted: 2006-9-25 15:42:00 |
Top |
fortran >> segmentation error: SIGSEGV
> You mean it is not wrong of my code but shell setting problem?
it is not necessarily a problem of your code. Ifort tends to generate
large temporary arrays on stack which causes programs to crash like
this if the default size the shell allows is not large enough. So, the
first thing to try is to increase the limit that your shell uses as a
default. If you use bash it will be
ulimit -s 128000
if you use tcsh
unlimit
or something similar.
echo $SHELL
will tell you what you use. It is also described in the documentation
that comes with ifort, but I forgot where.
Joost
|
| |
|
| |
 |
snfinder@naver.com

|
Posted: 2006-9-25 15:56:00 |
Top |
fortran >> segmentation error: SIGSEGV
> ulimit -s 128000
^^ Thanks again Joost
Ah~ Ifort was a problem...
By the way, does the stack limit value 128000 has a some meaning?
It just a few more progress after I execute that command.
I want more steps. Is is okay seting more number?
Umm... is this command safe?
I'm curious what effects the system will be affected.
PDS
|
| |
|
| |
 |
Joost

|
Posted: 2006-9-25 16:04:00 |
Top |
fortran >> segmentation error: SIGSEGV
snfinder@naver.com wrote:
> > ulimit -s 128000
>
> ^^ Thanks again Joost
> Ah~ Ifort was a problem...
> By the way, does the stack limit value 128000 has a some meaning?
> It just a few more progress after I execute that command.
>
> I want more steps. Is is okay seting more number?
>
> Umm... is this command safe?
> I'm curious what effects the system will be affected.
the command sets the stack size to 128Mb. If you set it to a somewhat
larger number it will go somewhat further, up to the point where you
run out of memory. Now, if you're simply doing some integration, there
is really no point to have the code generate such huge temporaries, and
I would suggest you write the DO loop that is equivalent to the 'SUM'
that is causing the problems.
Joost
|
| |
|
| |
 |
Kamaraju Kusumanchi

|
Posted: 2006-9-26 7:00:00 |
Top |
fortran >> segmentation error: SIGSEGV
Joost wrote:
> ulimit -s 128000
If you are worried about what number to set it from, just use
ulimit -a unlimited
and leave the rest of the details to the OS and hardware! This is what I do!
raju
--
http://kamaraju.googlepages.com/cornell-bazaar
http://groups.google.com/group/cornell-bazaar/about
|
| |
|
| |
 |
| |
 |
Index ‹ fortran |
- Next
- 1
- CVF Version 6.1.A BugThis version of the CVF compiler fails to compile this:
Type spline
Real*8, Allocatable:: b(:)
Real*8, Allocatable:: c(:,:)
Integer:: Info
End Type spline
Anyone knows where I can find the 6.6 upgrade hoping that it will
compile
Mike
- 2
- WRITE + new lineHi,
I want to write an 2-dimensional array to a textfile, but WRITE always
uses a new line. How can you stop that?
I use something like this:
DO i=1, length1
DO j=1, length2
WRITE(*,*) array(i,j)
END DO
END DO
I read that it shout be able to do something like this:
DO i=1, length1
WRITE(*,*) (array(i,j), j=1, length2)
END DO
but it still uses a new line for each entry.
Is there a convenient standard Fortran 90/95 way to do this?
Thanks,
Martin
- 3
- How old is the average Fortran programmer?Terence wrote:
> Getting really off the subject with 238 replies and only 88 different
> people; aren't we?
> Perhaps the children chatter so.
>
>
Could be worse, nobody has called anybody else a liar, racist,
or pedophile yet ;).
Dick Hendrickson
- 4
- undefined reference, possible causes?Hi Fortran masters,
I'm trying to compile some code, but I get errors like
undefined reference in '_Subroutine'
to function '_Function'
where both subroutine and function are both in the same module. I'm
stuck as to what's causing this. What I really don't get is that the
function is right there in the same module as the subroutine that uses
it, so how could it be an undefined refernce? Any ideas? Thanks
- 5
- Intel Fortran Linux: run time problemI am not entirely sure whether this is a compiler problem but I
suspect so, hence this post.
The following code is part of a program that basically produces a
command line to be passed to ImageMagick ("convert xyz"). It runs
perfectly under Windows after compilation with CVF using dflib, but
when compiled with IFC 7.1 under Linux (kernel 2.4.20-4) using iflport
I get the following run-time error messages:
sh: -c: line 1: unexpected EOF while looking for matching `"'
sh: -c: line 2: syntax error: unexpected end of file
This is the relevant bit of code:
******
character(200) &
chCols, &
chRows, &
chDataType, &
chDTPFile, &
chNewRSTFile, &
chInsetText*400, &
chCommand*500
logical(4) &
bResult
chInsetText = achar(39)//trim(chInsetText)//achar(39)
chCommand = 'convert -size'//trim(chCols)//'x'//trim(chRows)//&
' -depth '//trim(chDataType)//' -font helvetica -fill white'//&
' -gravity SouthEast -draw "text 10,20 '//trim(chInsetText)//&
'" gray:'//trim(chNewRSTfile)//' '//trim(chDTPFile)
bResult = systemqq (chCommand)
******
(linked with -Vaxlib, using iflport (dflib for CVF Windows))
When I add a
print*,chCommand
statement, I see that a line break is added at a seemingly random
location within the chCommand string. I guess that this is the root
of the problem but I don't know how to get rid of it.
Any ideas much appreciated!
Kind regards,
Jan Cermak
- 6
- if module file as one of the source files, compile is wrong? (using CVF6.6)Hi
First of all I'd like to say thanks to many guys here answering my
questions about module.
I started to use it.
I name my module file as "mod.f90" included in the beginning of main
program. I use Compaq Visual Fortran v6.6. When I compile the main
program, the module file is automatically
captured as an external dependencies (left dialogue box shows it).
When I finished modifying mod.f90. I compile it and CVF ask if I want
to insert it into the project. If I insert it,
it appears as one source file (shown in left dialogue box). Then
compiling is wrong.
So everytime I had to remember to click my mouse on the main program.
Then compiling is ok.
Do I do something wrong? Do I need to change the file extention of
mod.f90? Otherwise, why CVF asks me to
insert it as source file?
thank you.
Mike
- 7
- Allocatable Arrays As OutputsHi All,
first of all, please forgive my poor mastering of Fortran. I am
still a beginner who uses Fortran sporadically.
I have a subroutine in which I declare 4 output variables as
allocatable. This is because, a priori, I don't know their lengths
(they're all one-dimensional vectors), and I discover this information
only when I read a file which contains both their lengths and the data
used to fill these vectors.
My problem is, I don't know how to correctly "declare" these variables
in the main program, as I keep getting errors on assumed-shape/size
and dummy arguments. My knowledge of Fortran is so slim I can't find a
way to solve this problem.
I am attaching a simplified version of my small program (1 subroutine
+ the main) in which I have only 1 allocatable array. I have used my
google-fu but either I can't interpret correctly the problem or what I
am doing is completely wrong.
Thank you for all your suggestions.
Andrea.
subroutine ReadINSPEC(fileName, propertyNames)
use ReadECLIPSEBinary
implicit none
character (len=*), intent(in) :: filename
character (len=8), allocatable, intent(out) :: propertyNames(:)
integer numberOfProps
character (len=4) keywordType
character (len=8) keywordName
logical feof
open(unit=1, file=filename, form='UNFORMATTED',
convert='BIG_ENDIAN')
feof = .false.
while_loop: do while (.not.feof)
read(1, end=20, err=18) keywordName, numberOfProps,
keywordType
if (keywordName == 'NAME') then
allocate(propertyNames(numberOfProps))
call ReadECLIPSEData(1, numberOfProps,
stringVector=propertyNames)
exit while_loop
endif
18 continue
enddo while_loop
20 continue
deallocate(propertyNames)
close(1)
return
end subroutine ReadINSPEC
program main
! ???????
! I don't know if this is possible or not...
! ???????
character(len=14) :: fileName
character(len=8) :: propertyNames(:)
fileName = 'OPT_INJ.INSPEC'
call ReadINSPEC(fileName, propertyNames)
end program main
- 8
- increasing widthI've been writing a fortran95 prog and was getting nine significant figures
for a real-valued calculation.
Some fellow over in sci.math.num-analysis tells me I can get at least 6 more
sig figs, if instead of declaring as type real, I declare as real(8). My
compiler complains:
numsci1.F95(3) : error 62 - Invalid KIND specifier
warning : comment 981 - Specifying the kind of the type REAL with the
constant '8' is non-portable - 'SELECTED_REAL_KIND(6,37)' would be better.
The error is from the line:
real(8) :: total, term
, which I get every time I want to declare real(8). The warning that it
issues would seem to point to the way out. How do I make a real variable
with 'SELECTED_REAL_KIND(6,37)'?
- 9
- writing step by stephi
i work with fortran 90 in linux .
is any command in fortran which can write variables when program runs ?
i know i can wirte answer in file, but seeing the answers is possible
when running is ended .
in C , this command is "cout " , is it have eqaul command in fortran ?
thanks , nakisa
- 10
- unformatted files and record descriptorsIn looking for something else, I noticed a page about
converting unformatted file formats:
http://www.laheyforum.com/showthread.php?t=10235
There has been discussion here in the past about record
headers on unformatted files. As I understand it, an unformatted
READ reads one record (as written by one unformatted WRITE).
If the I/O list on the read is smaller than on the write the
rest of the record is ignored. It would seem without record
headers it would not be possible to know how long the original
record was, and so not possible to ignore the rest of the record.
Has this changed in newer standards, or are compilers ignoring
the standard?
-- glen
- 11
- 33.
--
-- --
-- I'm using a bst to kill bugs today. 32 kills so far. That is an
authentic task.
During sorting, the most important technique is pre-selection, the
neceassayrry method for sorters who last more than 2 weeks at ups. Sara was
the best before I walked into the building. King Rooster.
n s ? foot / hand
e w ? hand \ foot
No survivors for n, e> 0. La cooka rach tja.
--
-- --
--
Wade Ward
"In any given barnyard, there can be only one rooster."
Wade Ward
"I put my pants on like any other 6: between four and a dozen failures."
{~._.~} The Naked Picture Poster from Down Under
`( Y )`
- 12
- Compiling fortranposix on new machello
I just purchased a new mac, installed fink, gcc4 (includes gfortran) and
Xcode SDK (i think i installed gcc4 from xcode, but found it does not
include gfortran, so i reinstalled gcc4 from fink on top of that) from
apple.
I am trying to compile fortranposix on this machine. compilation of
posixwrapper is ok.
gcc-4 -c -o posixwrapper.o posixwrapper.c
i dont know how to use gfortran to create a shared library (.dylib), and
the following happens (see end of post).
how do i do it ?
thx,
Kemal.
-----------------------------
gfortran fortranposix.f90 posixwrapper.o -o fortranposix.dylib
/usr/bin/ld: warning suggest use of -bind_at_load, as lazy binding may
result in errors or different symbols being used
symbol _clogf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctanl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctanhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctanhf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctanh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctanf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ctan used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csqrtl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csqrtf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csqrt used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csinl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csinhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csinhf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csinh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csinf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _csin used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _creall$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _crealf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _creal used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cprojl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cprojf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cproj used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cpowl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cpowf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cpow used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _conjl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _conjf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _conj used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cabsf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cabsl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacos used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacosf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacosh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacoshf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacoshl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cacosl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _carg used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cargf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cargl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casin used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casinf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casinh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casinhf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casinhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _casinl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catan used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catanf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catanh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catanhf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catanhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _catanl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccos used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccosf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccosh used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccoshf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccoshl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ccosl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cexp used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cexpf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cexpl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cimag used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cimagf used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cimagl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _clog used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _clogl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(complex.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _tanf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _asinhf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _lgammaf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _atanf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _hypotf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _expm1f used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cosf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _coshf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _exp2f used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _erff used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _expf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _erfcf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log1pf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cbrtf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _logf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _atanhf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _atan2f used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _asinf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _sinf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _sinhf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _acoshf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _acosf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _sqrtf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log10f used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log2f used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _powf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _tanhf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _tgammaf used from dynamic library
/usr/lib/libSystem.dylib(floating.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _asinhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ArcHyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(single module)
symbol _acoshl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ArcHyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(single module)
symbol _atanhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ArcHyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(single module)
symbol _atanl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ArcTanDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _atan2l$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ArcTanDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _scalblnl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _copysignl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fabsl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fmaxl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _logbl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _scalbnl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ceill$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fdiml$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _floorl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fmal$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fminl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _fmodl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _frexpl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _hypotl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ilogbl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _ldexpl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _llrintl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _llroundl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _lrintl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _lroundl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _modfl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nanl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nearbyintl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nextafterl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nexttoward$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nexttowardf$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _nexttowardl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _remainderl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _remquol$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _rintl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _rinttoll used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _roundl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _truncl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(AuxiliaryDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _coshl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(HyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(single module)
symbol _sinhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(HyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(single module)
symbol _tanhl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(HyperbolicDD.o) not from earlier dynamic
library /usr/lib/libmx.A.dylib(singl/usr/bin/ld: Undefined symbols:
_MAIN__
e module)
symbol _cosl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(SinCosTanDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _sinl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(SinCosTanDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _tanl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(SinCosTanDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _exp2l$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ExpDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _expl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ExpDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _expm1l$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(ExpDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _logl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(LogDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log2l$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(LogDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log10l$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(LogDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _log1pl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(LogDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _sqrtl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(SqrtDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
symbol _cbrtl$LDBL128 used from dynamic library
/usr/lib/libSystem.dylib(SqrtDD.o) not from earlier dynamic library
/usr/lib/libmx.A.dylib(single module)
collect2: ld returned 1 exit status
- 13
- data-stmt-value-listRichard E Maine wrote:
(snip)
> The 999 says to repeat the following bit 999 times. If you might have
> more than 999 values on a line, bump that up as needed. It doesn't have
> to match the number of values; it just has to be at least large enough.
> The : says to stop there if there are no more data values. That's
> perhaps the trickiest part. It prevents you from having a superfluous
> trailing comma.
Initializations in C and Java allow for a trailing comma in the list.
This is convenient with conditional compilation using the C
preprocessor, and also for computer generated initializations, allowing
one to generate the extra comma without a test for the last element of
the list.
In my copy of N3501.pdf I can't see a definition for
data-stmt-value-list to see if a trailing comma is allowed or not.
(I used the search feature and still didn't find it.)
It looks a little strange, but it is convenient.
-- glen
- 14
- Need HelpHi all,
I am looking for a utility with source code given for converting
VAX fortran to Fortran90. Can someone provide the links or source code
which do the translation of VAX Fortran into Fortran90(f90).
thanks
xyz
- 15
- Is there any problem with the following program?I find the following program in a book:
program ex0413
character(len=20) string
string = "Good morning."
write(*, *) string
string(6) = "evening."
write(*, *) string
end
When it is complied by CVF, the following error is displayed:
Error: This name has not been declared as an array. [STRING]
string(6) = "evening."
So, can anyone tell me what is the problem? Thanks a lot.
|
|
|