public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "werner" <werner@copaya.yi.org> To: gcc-bugs@gcc.gnu.org Subject: f77 bug Date: Tue, 31 Jul 2007 22:54:00 -0000 [thread overview] Message-ID: <1185921783.31606@werner> (raw) [-- Attachment #1: Type: text/plain, Size: 675 bytes --] The f77 compiler seems to have a BUG what makes - for me - it impossible to use seriously I have a lot of very big old f77 progs, what I want to revise, and put open. f77 DONT PRODUCE A COMPILING LIST FILE, i.e. listing the source-code with line number and errors/warnings after each line !!!!!!!!!!!!!!!!!!!!! At least, since months im searching this possibility. Old-time compilers had this option, f.ex. compile with #f77 -l <file> or something like this I need this urgently. Without this, I cannot compile/adapt/make error-free these progs Pls. put in a new option, that f77 makes such a list at compiling time !!!!!!!!!!! w.landgraf werner@copaya.yi.org
reply other threads:[~2007-07-31 22:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1185921783.31606@werner \ --to=werner@copaya.yi.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).