public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "justinb at math dot berkeley dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/38316]  New: The "--help=xxx" option does not play well with -pipe or -save-temps
Date: Sat, 29 Nov 2008 09:54:00 -0000	[thread overview]
Message-ID: <bug-38316-16273@http.gcc.gnu.org/bugzilla/> (raw)

I ran into this issue running "gcc ${CFLAGS} -Q --help=optimizers", when
${CFLAGS} happened to contain -pipe.

When -pipe is turned on, the --help=xxx switch will cause the compiler to print
help to stdout, before its usual steps of dumping "help-dummy" assembly code
and letting the driver pipe its output to the assembler. For example:
$ gcc -pipe --help=target
{standard input}: Assembler messages:
{standard input}:1: Error: no such instruction: `the following options are
target specific:'
[snip]
{standard input}:88: Error: junk at end of line, first unrecognized character
is `-'

A related, but far more minor, problem occurs when -save-temps is passed with
--help=xxx. The help message is printed correctly, but afterwards the assembler
complains:
Assembler messages:
Error: can't open help-dummy.s for reading: No such file or directory

Thanks for your attention.


-- 
           Summary: The "--help=xxx" option does not play well with -pipe or
                    -save-temps
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: driver
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: justinb at math dot berkeley dot edu


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


             reply	other threads:[~2008-11-29  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29  9:54 justinb at math dot berkeley dot edu [this message]
2008-12-01  0:15 ` [Bug driver/38316] " pinskia 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=bug-38316-16273@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).