From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH REPOST] dtc: integrate gpp
Date: Sat, 25 Aug 2012 10:45:23 +0200 [thread overview]
Message-ID: <20120825084523.GD6060@game.jcrosoft.org> (raw)
In-Reply-To: <1345608667-16494-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 22:11 Tue 21 Aug , Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> I figured the easiest way to get named constants into dtc would be to
> re-use an existing C pre-processor implemntation. Surprisingly, I could
> not find many /good/ possibilities for this. I eventually found one called
> gpp. This patch is an extremely quick-and-dirty integration of gpp into
> dtc in order to solicit some feedback. What do people think of this
> approach in general?
>
> Issues:
> * Fails some test-cases, related to dependency file generation, reading from
> stdin and include search paths.
>
> TODO:
> * Needs to be split into many smaller patches, such as:
> + Add unmodified upstream gpp.c.
> + Various different modifications to gpp.c to make it compile within dtc.
> Some of these might be able to go back upstream to gpp.
> * Need a way to call gpp as a library, rather than faking a command-line for
> it. Perhaps this could go upstream too.
> * Need to use a pipe instead of a temp file to pass the result from gpp to
> dtc. Or, if we rework gpp as a library, some intra-process way of streaming
> the output between processing steps. Perhaps this could go upstream too, if
> they accept the gpp-as-a-library concept.
> * Need some better fixes for the const issues instead of xstrdup().
> * Need to implement search paths for gpp includes.
> * Probably more I forget; I originally prototyped this a while back.
> * Test suite failure fixes, although at least some would be addressed by the
> points above.
> ---
> Note: This patch is based on a slightly stale copy of dtc, plus some local
> patches for other work I've sent, some of which has been accepted upstream
> already, and some note. If this approach appeals to anyone, I will of course
> rebase this.
I'm not sure it's rely the right way
I does the support but we may just use gcc for as it's done for linker script
but I will agree that with this dtc is standalone
Best Regards,
next prev parent reply other threads:[~2012-08-25 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 4:11 [PATCH REPOST] dtc: integrate gpp Stephen Warren
[not found] ` <1345608667-16494-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-25 8:45 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
[not found] ` <20120825084523.GD6060-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-08-25 22:26 ` Stephen Warren
[not found] ` <d30e7f01-ead2-4b37-9bf9-ac4b5c18f936-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2012-08-26 15:16 ` Jean-Christophe PLAGNIOL-VILLARD
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=20120825084523.GD6060@game.jcrosoft.org \
--to=plagnioj-sclmfoaustbwk0htik3j/w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 NNTP newsgroup(s).