public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rep dot dot dot nop at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31588] gfortran should be able to output Makefile dependencies with -M* options
Date: Mon, 04 Jun 2007 20:50:00 -0000	[thread overview]
Message-ID: <20070604205020.12513.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31588-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from rep dot dot dot nop at gmail dot com  2007-06-04 20:50 -------
Subject: Re:  gfortran should be able to output Makefile dependencies with -M*
options

On Mon, Jun 04, 2007 at 05:39:48PM -0000, fxcoudert at gcc dot gnu dot org
wrote:
>
>
>------- Comment #5 from fxcoudert at gcc dot gnu dot org  2007-06-04 17:39 -------
>(In reply to comment #4)
>> fx, are you still working on this?
>
>Not actively. It's probably not so hard, though: read the file, like we do with
>-fsyntax-only mode, and parse #file headers.

Yes, without looking i was thinking about for each file, populate a list
of provides/needs mods and emit them when a file is done.

>> yet another reason why "-M" as an alias for -J should be dropped and instead
>> proper -M dependency handling should be added is this:
>> 
>> $ echo end > foo.f90 && gfortran -o main  foo.f90 -v -M
>> Segmentation fault
>
>That's another one. File a new PR (it's probably a simple check that's missing
>in gfc_handle_module_path_options()).

I did not look whether it is calling strlen on NULL or another spot in
the option handling, but i will not look at the current meaning of -M,
so please feel free to file this if you think it's worth noting it.
Thanks,


-- 


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


  parent reply	other threads:[~2007-06-04 20:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  9:21 [Bug fortran/31588] New: " fxcoudert at gcc dot gnu dot org
2007-04-16  9:22 ` [Bug fortran/31588] " fxcoudert at gcc dot gnu dot org
2007-04-16  9:22 ` fxcoudert at gcc dot gnu dot org
2007-04-16 10:02 ` dfranke at gcc dot gnu dot org
2007-04-16 10:06 ` fxcoudert at gcc dot gnu dot org
2007-04-16 14:28 ` burnus at gcc dot gnu dot org
2007-06-04 17:20 ` aldot at gcc dot gnu dot org
2007-06-04 17:40 ` fxcoudert at gcc dot gnu dot org
2007-06-04 20:50 ` rep dot dot dot nop at gmail dot com [this message]
2007-10-06 21:36 ` tkoenig at gcc dot gnu dot org
2008-01-30 22:57 ` dfranke at gcc dot gnu dot org
2008-01-31  1:47 ` fxcoudert at gcc dot gnu dot org
2008-03-26  3:33 ` pinskia at gcc dot gnu dot org
2008-03-26  3:36 ` pinskia at gcc dot gnu dot org
2008-05-25 22:56 ` dfranke at gcc dot gnu dot org
2010-05-03 18:10 ` dfranke at gcc dot gnu dot org
2010-06-12 21:06 ` dfranke at gcc dot gnu dot org
2010-06-12 21:46 ` dfranke at gcc dot gnu dot org
2010-06-13 16:05 ` dfranke at gcc dot gnu dot org
2010-06-13 16:07 ` dfranke at gcc dot gnu dot org
2010-08-07 16:52 ` jvdelisle at gcc dot gnu dot org
2010-08-08  1:59 ` jvdelisle at gcc dot gnu dot org

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