public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47472] New: Rules printed by -M option contains duplicate slash when -J option is used Date: Wed, 26 Jan 2011 11:08:00 -0000 [thread overview] Message-ID: <bug-47472-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47472 Summary: Rules printed by -M option contains duplicate slash when -J option is used Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: thenlich@users.sourceforge.net Example: testuse.f90: program testuse use testmake end program testuse testmake.f90: module testmake integer :: i, j end module testmake $ gfortran -Jobj -o obj/testmake.o -c testmake.f90 $ gfortran -Jobj -M -cpp testuse.f90 testuse.o: testuse.f90 obj//testmake.mod Expected output is: testuse.o: testuse.f90 obj/testmake.mod
next reply other threads:[~2011-01-26 10:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-26 11:08 thenlich at users dot sourceforge.net [this message] 2011-01-26 11:31 ` [Bug fortran/47472] " burnus at gcc dot gnu.org 2011-01-26 17:39 ` burnus at gcc dot gnu.org 2011-01-27 8:32 ` burnus at gcc dot gnu.org 2011-01-27 8:39 ` burnus at gcc dot gnu.org 2011-02-02 18:10 ` dnovillo at gcc dot gnu.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=bug-47472-4@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).