public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: [cygnus.bug-gcc] `-Q' switch to GCC is not documented; fix included
Date: Tue, 02 Dec 1997 16:29:00 -0000	[thread overview]
Message-ID: <sy90u38q8m.fsf@tiktok.cygnus.com> (raw)

I tend to agree with Nate's posting to bug-gcc, we probably should document
this in egcs.  I mean the switch has been valid since at least gcc 2 if not gcc
1.35 and beyond.

------- Start of forwarded message -------
From: eldredge@ap.net (Nate Eldredge)
Newsgroups: cygnus.bug-gcc
Subject: `-Q' switch to GCC is not documented; fix included
Date: 30 Nov 1997 10:58:57 -0800
Message-ID: <199711301858.KAA28290.cygnus.bug-gcc@adit.ap.net>
To: bug-gcc@prep.ai.mit.edu

The title pretty much says it. GCC's `-Q' option, which prints each
function's name as it is compiled, and prints some time statistics at the
end, isn't mentioned in the documentation, at least for GCC 2.7.2.1. Here is
a patch which adds it.

*** invoke.texi~	Tue Oct  3 15:40:43 1995
--- invoke.texi	Sun Nov 30 09:02:56 1997
***************
*** 1582,1587 ****
--- 1582,1591 ----
  however, that the format of the data is not what @code{tcov} expects.
  Eventually GNU @code{gprof} should be extended to process this data.
  
+ @item -Q
+ Makes the compiler print out each function name as it is compiled, and
+ print some statistics about each pass when it finishes.
+ 
  @item -d@var{letters}
  Says to make debugging dumps during compilation at times specified by
  @var{letters}.  This is used for debugging the compiler.  The file names

Nate Eldredge
eldredge@ap.net



------- End of forwarded message -------

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

             reply	other threads:[~1997-12-02 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-02 16:29 Michael Meissner [this message]
1997-12-02 12:16 ` Jeffrey A Law
1997-12-02 18:18   ` Info discrepancy Oleg Krivosheev
1997-12-02 18:18     ` Jeffrey A Law
1997-12-02 23:24       ` Joe Buck
1997-12-02 23:24         ` Jeffrey A Law

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=sy90u38q8m.fsf@tiktok.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    /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).