This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Gfortran does not compile dynamo (and others)
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Tobias Burnus <burnus at net-b dot de>
- Cc: Ignacio Fern?ndez Galv?n <jellby at yahoo dot com>, fortran at gcc dot gnu dot org
- Date: Tue, 23 Jan 2007 09:39:19 -0800
- Subject: Re: Gfortran does not compile dynamo (and others)
- References: <481579.57968.qm@web33004.mail.mud.yahoo.com> <45B63B59.5040400@net-b.de>
On Tue, Jan 23, 2007 at 05:44:09PM +0100, Tobias Burnus wrote:
>
> "signal 11" and "internal file was deleted" sound like Molcas/Gaussian
> error messages, grep the source code and try to find the condition which
> triggers this message. From there walk up (if possible) to the actual cause.
"signal 11" is normally a segmentation fault. This coincides
with an array index going out of bounds. The OP should add
-Wall and -fbounds-check to the gfortran options.
> (At that link it is claim that gfortran 4.1 is 30-40% slower than g77,
> which is something I don't believe is true any more. Unless, they found
> an area where gfortran really produces bad code. [sunf95 used to have
> one single statement wrong [nint returned int(anint())], which caused
> the runtime of one of my programs to double.])
If the gfortran used in the comparison is built with checking
enabled, one may see a slow down. Try a gfortran that is
configured with --disable-checking.
--
Steve