public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rayvt@comm.mot.com To: gcc-gnats@gcc.gnu.org Subject: c/9743: -MF only writes the info from the very last of multiple C files. Date: Tue, 18 Feb 2003 14:26:00 -0000 [thread overview] Message-ID: <20030218141739.13404.qmail@sources.redhat.com> (raw) >Number: 9743 >Category: c >Synopsis: -MF only writes the info from the very last of multiple C files. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Feb 18 14:26:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Ray Van Tassle >Release: 3.2.2 & 3.2.1 >Organization: >Environment: Reading specs from /users/rayvt/local/gcc322/lib/gcc-lib/sparc-sun-solaris2.6/3.2.2/specs Configured with: ../configure --prefix=/users/rayvt/local/gcc322 Thread model: posix gcc version 3.2.2 >Description: If you do "gcc -MG -MM -MF deps.mk file1.c file2.c file3.c" Then only the info for the last file (file3.c) is put in the output file (deps.mk). But if you do ">deps.mk" instead of "-MF", the info for all the files (1 & 2 & c) is there. It looks like maybe the file named by "-MF" is re-opened for write for each of the processed source files, and is therefore overwritten by each one. >How-To-Repeat: > gcc -MG -MM -MF deps.mk ../src/ip_inbound.c ../src/ip_mobile_info.c ../src/cfg_layer.c >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-02-18 14:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-18 14:26 rayvt [this message] 2003-02-18 21:06 Neil Booth
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=20030218141739.13404.qmail@sources.redhat.com \ --to=rayvt@comm.mot.com \ --cc=gcc-gnats@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).