public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25708] Module loading is not good at all
Date: Sat, 07 Jan 2006 05:10:00 -0000 [thread overview]
Message-ID: <20060107051008.25828.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25708-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-07 05:10 -------
Looking at the profile for PR 21130 makes me think fixing this bug will also
fix that one.
Oh. it is just as bad if we have module modulef declared in the same file as we
have to save it and then reload it which is just a waste of time.
To Paul:
Also fixing up the derived types after the fact is just wrong that was PR
25391.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paul dot richard dot thomas
| |at cea dot fr
OtherBugsDependingO| |21130, 25391
nThis| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25708
next prev parent reply other threads:[~2006-01-07 5:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 5:05 [Bug fortran/25708] New: " pinskia at gcc dot gnu dot org
2006-01-07 5:10 ` pinskia at gcc dot gnu dot org [this message]
2006-01-09 7:37 ` [Bug fortran/25708] " paul dot richard dot thomas at cea dot fr
2006-10-02 11:24 ` fxcoudert at gcc dot gnu dot org
2006-10-31 7:00 ` fxcoudert at gcc dot gnu dot org
2006-10-31 8:29 ` paul dot richard dot thomas at cea dot fr
2007-01-15 10:28 ` pault at gcc dot gnu dot org
2007-04-25 8:42 ` jb at gcc dot gnu dot org
2007-05-02 7:41 ` pault at gcc dot gnu dot org
[not found] <bug-25708-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 15:12 ` burnus at gcc dot gnu.org
2011-04-03 18:33 ` jvdelisle at gcc dot gnu.org
2011-04-04 11:51 ` pault at gcc dot gnu.org
2011-04-04 12:35 ` burnus at gcc dot gnu.org
2011-04-05 4:47 ` jvdelisle at gcc dot gnu.org
2011-04-05 5:25 ` jvdelisle at gcc dot gnu.org
2011-04-05 5:35 ` jb at gcc dot gnu.org
2011-04-10 17:47 ` jvdelisle at gcc dot gnu.org
2011-11-30 19:57 ` Joost.VandeVondele at mat dot ethz.ch
2011-12-01 7:30 ` Joost.VandeVondele at mat dot ethz.ch
2011-12-01 14:13 ` jb at gcc dot gnu.org
2011-12-03 13:29 ` jvdelisle at gcc dot gnu.org
2012-08-24 14:02 ` Joost.VandeVondele at mat dot ethz.ch
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=20060107051008.25828.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).