From: Jim Wilson <wilson@specifixinc.com>
To: Primrose.Mbanefo@Infineon.com
Cc: gcc@gcc.gnu.org
Subject: Re: Code generation
Date: Wed, 31 Mar 2004 06:29:00 -0000 [thread overview]
Message-ID: <406A1BC1.90002@specifixinc.com> (raw)
In-Reply-To: <855134C63EDB28488B2D815FE6BEEE610AC6D916@mucse003.eu.infineon.com>
Primrose.Mbanefo@Infineon.com wrote:
> I have seen a lot on the internet saying it is possible to retrieve the
> syntax tree created by gcc.
> I use gcc 2.95.2 on a solaris box and I can't seem to find out how to
> get the tree in a file.
You need a more recent version. -fdump-translation-unit appeared in
gcc-3.0.x.
These trees are deliberately incomplete. This is to prevent people from
trying to subvert the GPL by feeding the trees into proprietary
compilers. This is an inconvenience, but it is FSF policy, and we must
respect it.
There are additional tree dumping options in more recent gcc versions.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-03-31 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 19:23 Primrose.Mbanefo
2004-03-31 6:29 ` Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 23:58 Code Generation Colin McCormack
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 colin
1999-01-31 23:58 Colin McCormack
1999-01-31 23:58 ` Ken Raeburn
1999-01-31 23:58 ` Horst von Brand
1999-01-31 23:58 Colin McCormack
1999-01-31 23:58 ` Ken Raeburn
1999-01-31 23:58 ` Martin v. Loewis
1999-01-31 23:58 ` colin
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Martin v. Loewis
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=406A1BC1.90002@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=Primrose.Mbanefo@Infineon.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).