public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40958] module files too large
Date: Tue, 25 Jun 2013 09:33:00 -0000	[thread overview]
Message-ID: <bug-40958-4-KWvsDG7d6c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40958-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |WAITING

--- Comment #15 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> However, the fundamental(?) issue of module sizes growing exponentially 
> with deep module hierarchies still remains. The solution to that is to 
> not include transitive dependencies, which in turn would require a module 
> cache for good performance. Whether that is worth doing, and who is willing 
> and able to do it, is unclear.

Would not it be simpler to tell the users what they should do to avoid this
issue? If yes, what would be the basic rules?


  parent reply	other threads:[~2013-06-25  9:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40958-4@http.gcc.gnu.org/bugzilla/>
2011-11-25 19:24 ` Joost.VandeVondele at mat dot ethz.ch
2011-11-28 14:37 ` Joost.VandeVondele at mat dot ethz.ch
2011-11-28 17:58 ` Joost.VandeVondele at mat dot ethz.ch
2011-11-29 18:59 ` tkoenig at gcc dot gnu.org
2013-03-29 10:17 ` Joost.VandeVondele at mat dot ethz.ch
2013-04-09 18:35 ` jb at gcc dot gnu.org
2013-04-17 13:51 ` burnus at gcc dot gnu.org
2013-04-17 19:36 ` Joost.VandeVondele at mat dot ethz.ch
2013-06-22 13:38 ` dominiq at lps dot ens.fr
2013-06-22 19:45 ` jb at gcc dot gnu.org
2013-06-24  6:53 ` Joost.VandeVondele at mat dot ethz.ch
2013-06-25  9:33 ` dominiq at lps dot ens.fr [this message]
2013-06-25 18:06 ` anlauf at gmx dot de
2014-04-09  8:28 ` dominiq at lps dot ens.fr
2015-06-05 16:55 ` kargl at gcc dot gnu.org
2015-06-05 20:41 ` kargl at gcc dot gnu.org
2015-08-08 20:23 ` fxcoudert at gcc dot gnu.org
2009-08-04  9:02 [Bug fortran/40958] New: " jv244 at cam dot ac dot uk
2009-08-04  9:10 ` [Bug fortran/40958] " steven at gcc dot gnu dot org
2009-08-04 10:13 ` jv244 at cam dot ac dot uk

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-40958-4-KWvsDG7d6c@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).