From: Alexandre Oliva <aoliva@redhat.com>
To: Bolan.Meek@wcom.com
Cc: bolan@koyote.com, Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
gcc@gcc.gnu.org
Subject: Re: Compiler Directive to List Defined Macros?
Date: Wed, 28 Jun 2000 08:14:00 -0000 [thread overview]
Message-ID: <oru2edg7ns.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <395A1394.FECEE76A@wcom.com>
On Jun 28, 2000, Bolan Meek <Bolan.Meek@wcom.com> wrote:
> Alexandre Oliva wrote:
>>
>> On Jun 28, 2000, Bolan Meek <Bolan.Meek@wcom.com> wrote:
>>
>> > 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.
>>
>> Check the manual (info gcc). Such an option exists.
> OK! Search number two coming up!
Actually, Franz had already given you the option name (-dM), but I had
failed to notice it. He just didn't mention that you could feed gcc
-E your source file, instead of telling it to read from `- < /dev/null'.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-06-28 8:14 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
2000-06-28 7:56 ` Alexandre Oliva
2000-06-28 8:06 ` Bolan Meek
2000-06-28 8:14 ` Alexandre Oliva [this message]
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=oru2edg7ns.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=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).