public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/57784] GCC inadvertedly truncates source text
Date: Mon, 08 Jul 2013 08:37:00 -0000 [thread overview]
Message-ID: <bug-57784-4-7HYMFxzzCF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57784-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57784
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Joost.VandeVondele at mat dot ethz
| |.ch
--- Comment #3 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Marc Glisse from comment #2)
> Uh, what's wrong about using a heuristic and refusing to compile when the
> name of the output file ends in .c, .C, .cc, .f90, etc (possibly unless some
> -fweird-output-name is also passed) and the file already exists?
I would also be strongly in favor of such a simple heuristic... it is really a
common error that has bitten more than one user, including myself.
prev parent reply other threads:[~2013-07-08 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-57784-4@http.gcc.gnu.org/bugzilla/>
2013-07-08 4:56 ` pinskia at gcc dot gnu.org
2013-07-08 5:38 ` glisse at gcc dot gnu.org
2013-07-08 8:37 ` Joost.VandeVondele at mat dot ethz.ch [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=bug-57784-4-7HYMFxzzCF@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: 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).