public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files Date: Thu, 01 Sep 2011 01:28:00 -0000 [thread overview] Message-ID: <bug-49149-4-GnR2hVyLky@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49149-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49149 --- Comment #13 from Zaak <zbeekman at gmail dot com> 2011-09-01 01:27:46 UTC --- As for intrinsic F2003 modules, like ISO_C_BINDING, ISO_FORTRAN_ENV, etc. I would expect the compiler to be able to handle this appropriately, i.e. not require the presence of a iso_c_binding module in the build directory. Modules which are provided as compiler extensions to the Fortran standard should also be handled appropriately. My preference would be to exclude such intrinsic and compiler extension modules from the dependency list, but if a .mod file is installed with the compiler, the dependency could be given with a full path to its location. I can't think of an occasion when you would need a path to these intrinsic/extension modules, unless, perhaps, the tool were used while developing the compiler itself. Also, every time I read 'The dependencies take modules, Fortran's include, and CPP's #include into account.' I can't help but think that the creators of this feature were trying to make a useful tool which could handle Fortran specific, especially module, dependency resolution.
next prev parent reply other threads:[~2011-09-01 1:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-24 20:09 [Bug fortran/49149] New: " zbeekman at gmail dot com 2011-05-24 22:02 ` [Bug fortran/49149] " kargl at gcc dot gnu.org 2011-07-24 19:06 ` dfranke at gcc dot gnu.org 2011-08-31 20:06 ` zbeekman at gmail dot com 2011-08-31 20:24 ` zbeekman at gmail dot com 2011-08-31 21:06 ` kargl at gcc dot gnu.org 2011-08-31 22:18 ` zbeekman at gmail dot com 2011-08-31 22:28 ` sgk at troutmask dot apl.washington.edu 2011-08-31 22:46 ` zbeekman at gmail dot com 2011-08-31 23:05 ` zbeekman at gmail dot com 2011-08-31 23:21 ` sgk at troutmask dot apl.washington.edu 2011-09-01 1:14 ` zbeekman at gmail dot com 2011-09-01 1:28 ` zbeekman at gmail dot com [this message] 2011-09-03 14:47 ` zbeekman at gmail dot com 2011-11-07 22:52 ` fxcoudert at gcc dot gnu.org 2015-03-03 21:09 ` zbeekman at gmail dot com 2015-03-03 21:20 ` zbeekman at gmail dot com
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-49149-4-GnR2hVyLky@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: linkBe 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).