public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects
Date: Fri, 01 Oct 2010 08:13:00 -0000	[thread overview]
Message-ID: <20101001081300.tGWmg2zp55y6Xl3c5RPLCPWdqOte1dFef7CYHuI2_HI@z> (raw)
In-Reply-To: <bug-45827-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827

--- Comment #17 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-10-01 08:13:37 UTC ---
(In reply to comment #16)
> I have checked the f90/f03 combination again, there DEFINITELY IS A CORRELATION
> between mixing dialects and the error. Using -std=f2003 also fixed the problem.

The file extensions should not have any influence (unless you use it in the
Makefile to pass different flags); .f90 and .f03 simply tell the compiler that
the file is in free format while .f indicates a fixed format. Thus, many
compilers only recognize .f90 and not .f95/.f03/.f08. Some do (such as
gfortran).

-std=f2003 changes several things and thus could have some influence (though it
shouldn't).

I think there is somewhere a latent bug and maybe things like using -std=f2003
changes slightly the internal program path and the memory usage which allows it
to pass or to fail.

Though, without being able to reproduce it, it is extremely difficult to find
the problem. :-(


  parent reply	other threads:[~2010-10-01  8:13 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 11:49 [Bug fortran/45827] New: " boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 12:37 ` [Bug fortran/45827] " Joost.VandeVondele at pci dot uzh.ch
2010-09-29 12:44 ` [Bug fortran/45827] [4.6 Regression] ice in create_int_parameter_array Joost.VandeVondele at pci dot uzh.ch
2010-09-29 12:49 ` burnus at gcc dot gnu.org
2010-09-29 12:54 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 13:02 ` mikael at gcc dot gnu.org
2010-09-29 13:18 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 14:22 ` [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects mikael at gcc dot gnu.org
2010-09-29 14:30 ` mikael at gcc dot gnu.org
2010-09-29 14:30 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 14:59 ` mikael at gcc dot gnu.org
2010-09-30 10:19 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 10:44 ` burnus at gcc dot gnu.org
2010-09-30 17:47 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 18:39 ` burnus at gcc dot gnu.org
2010-10-01  6:52 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  7:57 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  8:13 ` burnus at gcc dot gnu.org [this message]
2010-10-01 14:39 ` jvdelisle at gcc dot gnu.org
     [not found] ` <20101001143948.D63711C0008C@msfrf2419.sfr.fr>
2010-10-01 15:17   ` Mikael Morin
2010-10-01 17:42 ` jvdelisle at gcc dot gnu.org
2010-10-21 12:28 ` janus at gcc dot gnu.org
2010-10-21 14:04 ` burnus at gcc dot gnu.org
2010-10-24 10:17 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-24 11:10 ` burnus at gcc dot gnu.org
2010-10-24 11:56 ` mikael at gcc dot gnu.org
2010-10-24 12:02 ` mikael at gcc dot gnu.org
2010-10-24 15:15 ` jvdelisle at gcc dot gnu.org
2010-10-24 15:48 ` mikael at gcc dot gnu.org
2010-10-24 18:57 ` jvdelisle at gcc dot gnu.org
2010-10-24 19:59 ` mikael at gcc dot gnu.org
2010-10-26 15:27 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-27  9:35 ` boschmann at tp1 dot physik.uni-siegen.de
2010-12-27  2:23 ` dfranke at gcc dot gnu.org
2010-12-27 14:22 ` [Bug fortran/45827] [4.6 Regression] mio_component_ref(): Component not found janus at gcc dot gnu.org
2010-12-27 14:27 ` dfranke at gcc dot gnu.org
2010-12-27 15:37 ` [Bug fortran/45827] [4.6 Regression] [OOP] " janus at gcc dot gnu.org
2010-12-27 22:18 ` dfranke at gcc dot gnu.org
2010-12-28  8:15 ` janus at gcc dot gnu.org
2010-12-28 12:23 ` dfranke at gcc dot gnu.org
2010-12-28 13:19 ` janus at gcc dot gnu.org
2010-12-28 17:27 ` dfranke at gcc dot gnu.org
2010-12-28 18:53 ` janus at gcc dot gnu.org
2010-12-28 21:22 ` janus at gcc dot gnu.org
2010-12-31 11:21 ` jakub at gcc dot gnu.org
2011-01-02 21:28 ` janus at gcc dot gnu.org
2011-01-03 12:56 ` boschmann at tp1 dot physik.uni-siegen.de
2011-01-03 13:14 ` janus at gcc dot gnu.org

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=20101001081300.tGWmg2zp55y6Xl3c5RPLCPWdqOte1dFef7CYHuI2_HI@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).