public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30285] gfortran excessive memory usage with COMMON blocks in modules
Date: Sat, 10 Nov 2007 00:00:00 -0000	[thread overview]
Message-ID: <20071109235954.29632.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30285-6318@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from fxcoudert at gcc dot gnu dot org  2007-11-09 23:59 -------
(In reply to comment #15)
> I wrote this code originally, and I agree with your analysis.

But regtesting doesn't agree with my analysis... in case of common with
bind(c,name="..."), this patch hampers the diagnosis of commons with the same
name but different labels. I've tried hard to get it rolling that way, because
I agree it's cleaner, but I couldn't. I'll propose a different approach (a
hack, to avoid writing twice the same combination of name and binding label) to
the list when it finishes regtesting.


-- 


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


  parent reply	other threads:[~2007-11-10  0:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  0:26 [Bug fortran/30285] New: gfortran huge (excessive?) memory usage with large modules anlauf at gmx dot de
2006-12-24  0:28 ` [Bug fortran/30285] " anlauf at gmx dot de
2006-12-24 10:47 ` [Bug fortran/30285] gfortran excessive " steven at gcc dot gnu dot org
2007-02-02  1:50 ` bdavis at gcc dot gnu dot org
2007-02-02  9:35 ` bdavis at gcc dot gnu dot org
2007-02-02 11:10 ` anlauf at gmx dot de
2007-02-02 21:44 ` anlauf at gmx dot de
2007-02-02 22:37 ` bdavis at gcc dot gnu dot org
2007-02-25  4:42 ` bdavis at gcc dot gnu dot org
2007-02-26 13:05 ` anlauf at gmx dot de
2007-04-13 18:44 ` tobi at gcc dot gnu dot org
2007-04-20  2:41 ` bdavis at gcc dot gnu dot org
2007-04-20 19:56 ` bdavis at gcc dot gnu dot org
2007-10-22  7:35 ` [Bug fortran/30285] gfortran excessive memory usage with COMMON blocks in modules anlauf at gmx dot de
2007-11-09 12:36 ` fxcoudert at gcc dot gnu dot org
2007-11-09 12:44 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2007-11-10  0:00 ` fxcoudert at gcc dot gnu dot org [this message]
2007-11-10  1:16 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2007-11-10  4:01 ` patchapp at dberlin dot org
2007-11-10 12:29 ` burnus at gcc dot gnu dot org
2007-11-10 15:18 ` anlauf at gmx dot de
2007-11-10 18:09 ` fxcoudert at gcc dot gnu dot org
2007-11-11 22:18 ` anlauf at gmx dot de
2007-11-12  5:55 ` patchapp at dberlin dot org
2007-11-17 13:47 ` fxcoudert at gcc dot gnu dot org
2007-11-17 13:49 ` fxcoudert at gcc dot gnu dot org
     [not found] <bug-30285-4@http.gcc.gnu.org/bugzilla/>
2015-10-10  9:12 ` dominiq at lps dot ens.fr

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=20071109235954.29632.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).