public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marco at hulten dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46010] New: reading of structure
Date: Wed, 13 Oct 2010 20:59:00 -0000 [thread overview]
Message-ID: <bug-46010-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010
Summary: reading of structure
Product: gcc
Version: 4.5.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: marco@hulten.org
Created attachment 22032
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22032
program with the struct and input namelist file
I compiled the NEMO ocean model (revision 1162) with gfortran. If I now run
the program, I get nonsense (random memory) data written in the 2nd, 4th, 6th
etc. ocean tracer entry in my output. The relevant code and namelist file
needed for compilation and the relevant output are attached to this e-mail.
This problem arises with gfortran 4.1.2 (RHEL), 4.4.5 (Debian) and 4.5.1
(Arch), but it doesn't with the Intel Fortran Compiler (ifort). Please let me
know if you need other information.
next reply other threads:[~2010-10-13 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 20:59 marco at hulten dot org [this message]
2010-10-13 21:42 ` [Bug fortran/46010] I/O: Namelist-reading bug burnus at gcc dot gnu.org
2010-10-14 3:20 ` jvdelisle at gcc dot gnu.org
2010-10-14 3:33 ` jvdelisle at gcc dot gnu.org
2010-10-14 8:09 ` burnus at gcc dot gnu.org
2010-10-14 18:16 ` marco at hulten dot org
2010-10-14 19:13 ` jvdelisle at gcc dot gnu.org
2010-10-25 5:48 ` jvdelisle at gcc dot gnu.org
2010-10-25 13:12 ` jvdelisle at gcc dot gnu.org
2010-10-26 1:37 ` jvdelisle at gcc dot gnu.org
2010-10-26 9:13 ` marco at hulten dot org
2010-10-26 19:05 ` jvdelisle at gcc dot gnu.org
2010-10-26 19:34 ` jvdelisle at gcc dot gnu.org
2010-10-26 19:37 ` jvdelisle at gcc dot gnu.org
2010-11-02 20:29 ` marco at hulten dot org
2010-11-04 0:17 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:25 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:34 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:38 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:42 ` jvdelisle 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=bug-46010-4@http.gcc.gnu.org/bugzilla/ \
--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).