https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
--- Comment #15 from Dominique d'Humieres ---
Related to pr82215. Submodules should probably also documented.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
Gary Howell gwhowell at ncsu dot edu changed:
What|Removed |Added
CC||gwhowell at ncsu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
Harald Anlauf anlauf at gmx dot de changed:
What|Removed |Added
CC||anlauf at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
Dominique d'Humieres dominiq at lps dot ens.fr changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
--- Comment #12 from kargl at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #11)
What should we do with this PR?
See my comment #1 and #10. I think that the PR
should be closed with WONTFIX (because gcc does not
have
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
nightstrike nightstrike at gmail dot com changed:
What|Removed |Added
CC||nightstrike at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
--- Comment #8 from envite at rolamasao dot org 2010-04-05 10:00 ---
I do not care particularly about automake and such, but precisely because the
Fortran standard does not say a word about module files the user expects to get
info about them _for his compiler_ in _his compiler
--- Comment #5 from rwild at gcc dot gnu dot org 2010-04-04 08:40 ---
(In reply to comment #1)
should -c explain how a .mod file is created?
IMHO, the answer is a resounding 'no.' Adding such information
would simply add unneeded clutter to the manual, and should be
an insult to
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-04-04 15:02
---
That idea of a --clean is interesting. I can see where it would be useful to
force a recompile of module files. I am not sure what the actual flag should
be. Of course one could use make to do all of this.
--
--- Comment #7 from kargl at gcc dot gnu dot org 2010-04-04 20:28 ---
(In reply to comment #5)
(In reply to comment #1)
should -c explain how a .mod file is created?
IMHO, the answer is a resounding 'no.' Adding such information
would simply add unneeded clutter to the
--- Comment #4 from jv244 at cam dot ac dot uk 2010-04-02 05:29 ---
(In reply to comment #2)
I think .mod files are not obvious; the standard does not say anything about
them, though (almost?) all compilers use them. On the other hand, few people
seem to have problems with .mod
--- Comment #2 from burnus at gcc dot gnu dot org 2010-01-06 14:16 ---
I think a description does not belong into man gfortran (invoke.texi), but
maybe into the general text of gfortran.texi.
I think .mod files are not obvious; the standard does not say anything about
them, though
--- Comment #1 from kargl at gcc dot gnu dot org 2010-01-05 05:49 ---
(In reply to comment #0)
[forwarded from http://bugs.debian.org/501560]
gfortran documentation lacks any kind of info about how to create a module
.mod file. It should be quite easy to indicate that the standard
15 matches
Mail list logo
