public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bolan Meek <Bolan.Meek@wcom.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: bolan@koyote.com, gcc@gcc.gnu.org
Subject: Re: Compiler Directive to List Defined Macros?
Date: Wed, 28 Jun 2000 07:35:00 -0000	[thread overview]
Message-ID: <395A0C74.CBE4F7C1@wcom.com> (raw)
In-Reply-To: <4.3.2.7.2.20000628162558.03ab8100@mail.lauterbach.com>

Franz Sirl wrote:
> 
> At 15:42 28.06.00, Bolan Meek wrote:
> >Greetings:  God bless you.
> >
> >I've searched `info gcc` and the mailing list archives,
> >but have found nothing on this:
> >
> >Is there any compiler directive that will cause a listing
> >of defined macros to be printed to stdout or stderr?
> >A #pragma something, perhaps?
> 
> Try
> 
> gcc -E -ansi -dM - </dev/null
> 
> Franz.

Thanks;  I tried it.  It looks like it supplies pre-defined
macros;  I was hoping for a compiler directive that would
also spit out the macros that have been defined in the
source code, during compilation.

Maybe I should send this in as a 'wishlist' item.

  reply	other threads:[~2000-06-28  7:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28  6:44 Bolan Meek
2000-06-28  7:27 ` Franz Sirl
2000-06-28  7:35   ` Bolan Meek [this message]
2000-06-28  7:56     ` Alexandre Oliva
2000-06-28  8:06       ` Bolan Meek
2000-06-28  8:14         ` Alexandre Oliva
2000-06-28 17:19 Ross Combs
2000-06-28 19:40 ` Geoff Keating
2000-06-29  0:39 ` Martin v. Loewis
2000-06-29  8:18 Ross Combs
2000-06-29 11:38 ` Geoff Keating
2000-06-29  8:28 Ross Combs
2000-06-29 13:44 ` Martin v. Loewis
2000-06-29 15:49 Ross Combs
2000-06-30  1:36 ` Neil Booth
2000-06-30 14:34 Ross Combs

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=395A0C74.CBE4F7C1@wcom.com \
    --to=bolan.meek@wcom.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=bolan@koyote.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).