From: Hans-Peter Nilsson <hp@bitrange.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, RFC] Dumping expanded MD files
Date: Sat, 24 Nov 2012 03:00:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1211232145570.40929@dair.pair.com> (raw)
In-Reply-To: <CAGs3RfvHEekrCcagF3uvFgsOfW+xLzFyi+RyoEY+qNkNa=-k3w@mail.gmail.com>
On Thu, 22 Nov 2012, Kirill Yukhin wrote:
> Hi folks,
>
> This patch adds an utility for dumping MD-files after iterators and
> define_substs expanding. The new utility is named genmddump and is
> built along with other gen* programs.
>
> I also added new target to Makefile to invoke this utility. However,
> I?m not sure it?s general enough to be added to the top-level
> makefile, so your suggestions on where we should place it and how it
> should be invoked are welcome.
> What do you guys think?
Very nice.
I think it should be enabled and the expanded md be dumped for
non-release builds.
There's configury bits for the development stage but with loose
ends; you'll have to add an AC_SUBST in gcc/configure.ac to use
in gcc/Makefile.in, like a @maybe_dumped_md@ set to empty or
s-mddump and added to dependencies for "all" (or probably
actually some suitable sub-dependency for "all").
brgds, H-P
next prev parent reply other threads:[~2012-11-24 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 17:49 Kirill Yukhin
2012-11-23 9:26 ` Mike Stump
2012-11-24 3:00 ` Hans-Peter Nilsson [this message]
2012-11-27 17:34 ` Richard Henderson
2012-11-29 7:22 ` Michael Zolotukhin
2012-11-29 18:41 ` Richard Henderson
2012-11-29 19:06 ` Richard Henderson
2012-11-30 9:10 ` Michael Zolotukhin
2012-11-30 19:13 ` Richard Henderson
2012-12-04 12:59 ` Kirill Yukhin
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.BSF.2.02.1211232145570.40929@dair.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kirill.yukhin@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).