public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "KnowlesPJ at Cardiff dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35892] gfortran lost memory blocks
Date: Thu, 24 Apr 2008 09:35:00 -0000	[thread overview]
Message-ID: <20080424093450.23287.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35892-14459@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from KnowlesPJ at Cardiff dot ac dot uk  2008-04-24 09:34 -------
As the originator of this report, I just wanted to add a context comment in
case it is helpful. This construction (common declared both in the module and
in subroutines (contained or external)) is horrible, but one of our developers
has found it to be the only reasonable way of dragging in a dusty deck.
Although the compiler crash was reported, this is not our main interest, since
the compiler seems to crash only with -g. Without -g, at any optimization
level, we are getting wrong numbers at run time. Abstracting that from the 1.5
million line code for a reasonable test case to report will not be easy, so we
are hoping that the fix to the compiler crash will be the silver bullet.


-- 


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


  parent reply	other threads:[~2008-04-24  9:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 17:24 [Bug fortran/35892] New: gfortran dies on file containing module and common KnowlesPJ at Cardiff dot ac dot uk
2008-04-09 17:25 ` [Bug fortran/35892] " KnowlesPJ at Cardiff dot ac dot uk
2008-04-09 18:32 ` [Bug fortran/35892] [4.4 regression] " burnus at gcc dot gnu dot org
2008-04-13 20:46 ` tkoenig at gcc dot gnu dot org
2008-04-18 14:42 ` jvdelisle at gcc dot gnu dot org
2008-04-18 15:10 ` jvdelisle at gcc dot gnu dot org
2008-04-18 16:24 ` jvdelisle at gcc dot gnu dot org
2008-04-18 17:13 ` kargl at gcc dot gnu dot org
2008-04-18 17:45 ` jvdelisle at gcc dot gnu dot org
2008-04-18 19:49 ` kargl at gcc dot gnu dot org
2008-04-18 21:28 ` jvdelisle at gcc dot gnu dot org
2008-04-18 21:32 ` jvdelisle at gcc dot gnu dot org
2008-04-19  0:08 ` kargl at gcc dot gnu dot org
2008-04-19  6:44 ` jvdelisle at gcc dot gnu dot org
2008-04-19  6:51 ` jvdelisle at gcc dot gnu dot org
2008-04-19  6:53 ` jvdelisle at gcc dot gnu dot org
2008-04-19 12:09 ` george at gcc dot gnu dot org
2008-04-19 21:12 ` [Bug fortran/35892] gfortran lost memory blocks jvdelisle at gcc dot gnu dot org
2008-04-24  8:30 ` george at gcc dot gnu dot org
2008-04-24  9:35 ` KnowlesPJ at Cardiff dot ac dot uk [this message]
2008-04-24 19:05 ` jvdelisle at gcc dot gnu dot org
2008-04-24 19:11 ` jvdelisle at gcc dot gnu dot org
2008-04-25  8:10 ` KnowlesPJ at Cardiff dot ac dot uk
2008-04-26  9:47 ` george at gcc dot gnu dot org
2008-04-26 10:19 ` george at gcc dot gnu dot org
2008-04-27  1:09 ` jvdelisle at gcc dot gnu dot 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=20080424093450.23287.qmail@sourceware.org \
    --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).