public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tom Browder" <tom.browder@gmail.com>
To: "Andrew Haley" <aph@redhat.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Debugging Macros
Date: Thu, 24 Jan 2008 11:18:00 -0000	[thread overview]
Message-ID: <8bc817ee0801230425t21a4ffa6hfba76d2d87093978@mail.gmail.com> (raw)
In-Reply-To: <47972F71.4080007@redhat.com>

On Jan 23, 2008 6:13 AM, Andrew Haley <aph@redhat.com> wrote:
> Tom Browder wrote:
...
> > Is there an easy way (such as defining an environment variable in the
> > build environment) to get the gcc build system to show the
> > preprocessed code to help backtrack the problem?
...
> Set your CC when running make: "make CC='gcc -g -save-temps -Wp,-dD ...'
>
> This will give you all macro definitions, expanded in .i files.
>
> For extra credit, run the .i files through GNU indent.

Thanks, Andrew.

-Tom

      reply	other threads:[~2008-01-23 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24  8:29 Tom Browder
2008-01-24  8:46 ` Andrew Haley
2008-01-24 11:18   ` Tom Browder [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=8bc817ee0801230425t21a4ffa6hfba76d2d87093978@mail.gmail.com \
    --to=tom.browder@gmail.com \
    --cc=aph@redhat.com \
    --cc=gcc-help@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).