public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/32528] -save-temps when compiling standard input fails
Date: Tue, 13 Nov 2007 03:27:00 -0000 [thread overview]
Message-ID: <20071113032726.2284.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32528-11211@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from manu at gcc dot gnu dot org 2007-11-13 03:27 -------
This is confirmed. I think the problem is in the specs in gcc.c:
%{!combine:\
%{save-temps|traditional-cpp|no-integrated-cpp:%(trad_capable_cpp) \
%(cpp_options) -o %{save-temps:%b.i} %{!save-temps:%g.i} \n\
cc1 -fpreprocessed %{save-temps:%b.i} %{!save-temps:%g.i} \
%(cc1_options)}\
%{!save-temps:%{!traditional-cpp:%{!no-integrated-cpp:\
when cc1 -fpreprocessed %{save-temps:%b.i} is expanded to cc1 -fpreprocessed
-.i
No idea how this can be fixed without a "--" or an "--input" option.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-11-13 03:27:26
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32528
next prev parent reply other threads:[~2007-11-13 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 23:05 [Bug c/32528] New: " mec at google dot com
2007-11-13 3:27 ` manu at gcc dot gnu dot org [this message]
2007-11-13 4:46 ` [Bug c/32528] " dsh at gcc dot gnu dot org
2007-11-13 4:51 ` dsh at gcc dot gnu dot org
2007-11-13 5:00 ` manu at gcc dot gnu dot org
2007-11-13 5:03 ` manu at gcc dot gnu dot org
2007-12-17 15:26 ` manu at gcc dot gnu dot org
2007-12-17 15:49 ` bonzini at gnu dot org
2008-01-25 21:16 ` rguenth at gcc dot gnu dot org
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=20071113032726.2284.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).