public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at eyesopen dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/16118] Preprocessed source error with -xf77-cpp-input
Date: Tue, 28 Dec 2004 14:45:00 -0000	[thread overview]
Message-ID: <20041228144535.14809.qmail@sourceware.org> (raw)
In-Reply-To: <20040621175602.16118.edwardss@whl.co.uk>


------- Additional Comments From roger at eyesopen dot com  2004-12-28 14:45 -------
The consensus amongst GCC developers is that it would be incorrect/unsafe to
preserve the ".f" file in the shared system /tmp area.  The only reason that
the preprocessed .f file is being placed in /tmp, is to avoid overwriting the
user's source file foo.f in the current directory.  The appropriate solution,
as I've now documented in the GCC manual, is that when explicitly using "-x",
if you require a particular intermediate file from -save-temps, you need to
ensure that it's file name doesn't conflict with the input source name.

In your example, the input source file could be renamed foo.F (as you suggest),
or foo.for, or foo.fpp etc... or perhaps placed in a different subdirectory.

Although not a bug, this PR could potentially be considered an "enhancement
request", but the difficultly of generating a unique file name in the current
directory and informing the user of it's location, would be a technically
complex work-around for what would be considered by many a "user error".
The "-x" and "--language" command line options should be used with care and
are far less preferrable to using the "conventional" file extensions for the
various source file formats.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


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


      parent reply	other threads:[~2004-12-28 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 17:56 [Bug fortran/16118] New: " edwardss at whl dot co dot uk
2004-07-11 16:01 ` [Bug fortran/16118] " tobi at gcc dot gnu dot org
2004-08-14  7:43 ` [Bug driver/16118] " pinskia at gcc dot gnu dot org
2004-12-28  4:24 ` cvs-commit at gcc dot gnu dot org
2004-12-28 14:45 ` roger at eyesopen dot com [this message]

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