linux-kernel - Re: dtc: import latest upstream dtc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <3C5DD611-6F36-4D13-9A88-377A8E30AAA5@kernel.crashing.org>
Date:	Sat, 13 Oct 2012 15:42:35 +0200
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	David Gibson <david@...son.dropbear.id.au>
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

> 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".

>   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?  The # and ## stringification
and token pasting ops will of course bite you with the ISO C pre- 
processor,
indeed.


Segher

--
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/