From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH] dtc: Basic integer expressions Date: Mon, 09 Apr 2012 21:48:33 -0600 Message-ID: <4F83AD91.1060507@wwwdotorg.org> References: <1333508160-7015-1-git-send-email-swarren@wwwdotorg.org> <20120410023807.GF29577@game.jcrosoft.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120410023807.GF29577-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Jean-Christophe PLAGNIOL-VILLARD Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org On 04/09/2012 08:38 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 20:56 Tue 03 Apr , Stephen Warren wrote: >> Written by David Gibson . Additions by me: >> * Ported to ToT dtc. >> * Renamed cell to integer throughout. >> * Implemented value range checks. >> * Allow U/L/UL/LL/ULL suffix on literals. >> * Enabled the commented test. >> >> Signed-off-by: Stephen Warren >> --- >> v3: >> * Fix printf warning by s/%ld/%zd/ >> * Support plain "U" as an integer literal suffix >> * Fix misplaced semi-colons in grammar >> * Support integer expressions for /memreserve/ and /incbin/ too >> * Modify eval_literal to check U/L suffixes after strtoull call, >> using strspn/strlen >> * Remove mention of libfdt from comment in tests/integer-expressions.c >> * Add comment to explain integer_prim range check >> v2: >> * s/cell/integer/ throughout. >> * Allow signed-extended values to pass the overall cell range check. >> * Allow L/UL/LL/ULL suffix on literals. This is purely for compatibility >> with C, and has no effect on dtc's processing. >> * Enabled the 3 disabled tests. > > Stephen what is the status of the define value? You mean /define/ VAR VALUE? It's on hold right now; I've been waiting for this patch to be merged before trying to push that, since one of the objections against the /define/ patch was that we didn't know what the future dtc expressions syntax would look like, and hence couldn't tell whether /define/ fit into it. Now at least we know what integer expressions look like, so can perhaps start thinking about /define/ syntax again...