From: Alexander Monakov <amonakov@ispras.ru>
To: noloader@gmail.com
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Expanding and debugging macros
Date: Sat, 27 Jun 2020 14:47:21 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.2006271446260.6255@monopod.intra.ispras.ru> (raw)
In-Reply-To: <CAH8yC8kQkPfja1jEQY+kF_JmR=ciW4kQH4aghKPRLrAFHLnUsw@mail.gmail.com>
On Sat, 27 Jun 2020, Jeffrey Walton via Gcc-help wrote:
> Is there a way to achieve this using GCC without changing the source files?
Did you inspect the preprocessed file? It still has line directives pointing
to the original source. You'll need to remove them.
Alexander
next prev parent reply other threads:[~2020-06-27 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 11:23 Jeffrey Walton
2020-06-27 11:47 ` Alexander Monakov [this message]
2020-06-27 17:12 ` Edward Diener
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=alpine.LNX.2.20.13.2006271446260.6255@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=noloader@gmail.com \
/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).