[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121014001641.GI4640@truffula.fritz.box>
Date: Sun, 14 Oct 2012 10:16:41 +1000
From: David Gibson <david@...son.dropbear.id.au>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: Stephen Warren <swarren@...dotorg.org>,
Scott Wood <scottwood@...escale.com>,
Michal Marek <mmarek@...e.cz>,
devicetree-discuss@...ts.ozlabs.org,
Stephen Warren <swarren@...dia.com>,
linux-kernel@...r.kernel.org
Subject: Re: dtc: import latest upstream dtc
On Sat, Oct 13, 2012 at 03:42:35PM +0200, Segher Boessenkool wrote:
> >Oh, that's strange. I'm pretty sure I've used -x assembler when I've
> >experimented with using cpp on dts manually before, and it seems to
> >have worked.
>
> Maybe you used "-x assembler-with-cpp"? That should work better ;-)
> Or just use the "-traditional-cpp" option, i.e. "gcc -E
> -traditional-cpp".
Ah, yes, assembler-with-cpp, that's the one I used.
> > Note that IIRC with gcc cpp, -x assembler also means
> >that # won't be handled as a cpp directive except in column 0 which is
> >also an advantage for us, although no longer essential with your
> >escaping support. Not all cpps have an equivalent option, though.
>
> This is how the traditional C pre-processor behaves. I don't think
> this is exactly what matters for DTS, or does it ever happen that
> you have a # preceded only by whitespace?
Uh.. pretty much whenever you define a #address-cells or #size-cells
property. At least until Stephen's patch to allow escaping that.
> The # and ## stringification
> and token pasting ops will of course bite you with the ISO C pre-processor,
> indeed.
>
>
> Segher
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists