From: "Vidya Praveen" <praveen@poseidontech.com>
To: <gcc@gcc.gnu.org>, "Alan Lehotsky" <apl@alum.mit.edu>
Cc: <apl@carbondesignsystems.com>
Subject: Re: G++ tree printouts?
Date: Wed, 18 Dec 2002 01:40:00 -0000 [thread overview]
Message-ID: <004701c2a667$9c159e60$1d01a8c0@blr.vsnl.net.in> (raw)
In-Reply-To: <a05200e03ba24cf790b60@[10.0.1.201]>
hi
use -fdump-tree- option.
(please refer to section 3.9/Debugging Options in Using the GCC Compiler
Collection Manual).
VP
http://www.geocities.com/vidyapraveen/
----- Original Message -----
From: "Alan Lehotsky" <apl@alum.mit.edu>
To: <gcc@gcc.gnu.org>
Cc: <apl@carbondesignsystems.com>
Sent: Tuesday, December 17, 2002 6:28 PM
Subject: G++ tree printouts?
> I know I could go grovel in the source code, but....
>
> Are there specific flags for dumping C++ tree information (in
> addition to the usual -dXXXX
> flags for dumping the RTL information)?
>
>
> --
> Carbon Design Systems, Inc.
> apl@carbondesignsystems.com
> 781-890-1500 x204
prev parent reply other threads:[~2002-12-18 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 8:58 Alan Lehotsky
2002-12-18 1:40 ` Vidya Praveen [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='004701c2a667$9c159e60$1d01a8c0@blr.vsnl.net.in' \
--to=praveen@poseidontech.com \
--cc=apl@alum.mit.edu \
--cc=apl@carbondesignsystems.com \
--cc=gcc@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).