public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug driver/57784] GCC inadvertedly truncates source text
[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
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-07-08 4:56 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57784
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is hard to fix and will not be fixed as gcc does not know it is writing to
a source file or a file you just happen to name to end with .cc . -lstdc++ is
considered an object file enough to link with which is why you see this
behavior with that only.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug driver/57784] GCC inadvertedly truncates source text
[not found] <bug-57784-4@http.gcc.gnu.org/bugzilla/>
2013-07-08 4:56 ` [Bug driver/57784] GCC inadvertedly truncates source text 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
2 siblings, 0 replies; 3+ messages in thread
From: glisse at gcc dot gnu.org @ 2013-07-08 5:38 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57784
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> This is hard to fix and will not be fixed as gcc does not know it is writing
> to a source file or a file you just happen to name to end with .cc .
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug driver/57784] GCC inadvertedly truncates source text
[not found] <bug-57784-4@http.gcc.gnu.org/bugzilla/>
2013-07-08 4:56 ` [Bug driver/57784] GCC inadvertedly truncates source text 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
2 siblings, 0 replies; 3+ messages in thread
From: Joost.VandeVondele at mat dot ethz.ch @ 2013-07-08 8:37 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-07-08 8:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-57784-4@http.gcc.gnu.org/bugzilla/>
2013-07-08 4:56 ` [Bug driver/57784] GCC inadvertedly truncates source text 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 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).