public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd: avoid decimal conversion
Date: Wed, 9 Oct 2019 19:28:50 +0200	[thread overview]
Message-ID: <e8cec620-ca45-eb41-a7d2-b8b25ded760d@gmail.com> (raw)
In-Reply-To: <20191009162651.GP6716@bill-the-cat>

Am 09.10.2019 um 18:26 schrieb Tom Rini:
> On Tue, Oct 08, 2019 at 10:48:39AM +0200, Michal Simek wrote:
>> Hi Tom,
>>
>> On 19. 09. 19 15:28, Michal Simek wrote:
>>> On 13. 09. 19 17:09, Tom Rini wrote:
>>>> On Wed, Sep 11, 2019 at 03:39:53PM +0200, Michal Simek wrote:
>>>>
>>>>> From: T Karthik Reddy <t.karthik.reddy@xilinx.com>
>>>>>
>>>>> This patch uses auto instead of decimal in simple_strtoul().
>>>>>
>>>>> Signed-off-by: T Karthik Reddy <t.karthik.reddy@xilinx.com>
>>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>>> ---
>>>>>
>>>>>   cmd/test.c | 24 ++++++++++++------------
>>>>>   1 file changed, 12 insertions(+), 12 deletions(-)
>>>>>
>>>>> diff --git a/cmd/test.c b/cmd/test.c
>>>>> index fa0c349f0827..258bfd880653 100644
>>>>> --- a/cmd/test.c
>>>>> +++ b/cmd/test.c
>>>>> @@ -113,28 +113,28 @@ static int do_test(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
>>>>>   			expr = strcmp(ap[0], ap[2]) > 0;
>>>>>   			break;
>>>>>   		case OP_INT_EQ:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) ==
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) ==
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_INT_NEQ:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) !=
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) !=
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_INT_LT:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) <
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) <
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_INT_LE:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) <=
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) <=
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_INT_GT:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) >
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) >
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_INT_GE:
>>>>> -			expr = simple_strtol(ap[0], NULL, 10) >=
>>>>> -					simple_strtol(ap[2], NULL, 10);
>>>>> +			expr = simple_strtol(ap[0], NULL, 0) >=
>>>>> +					simple_strtol(ap[2], NULL, 0);
>>>>>   			break;
>>>>>   		case OP_FILE_EXISTS:
>>>>>   			expr = file_exists(ap[1], ap[2], ap[3], FS_TYPE_ANY);
>>>>
>>>> I'm going to NAK this, but could be argued around to changing my mind.
>>>> While it's true that in general command inputs are hex and not decimal,
>>>> this has been decimal since introduction in 2009.  So changing it now is
>>>> breaking ABI and other peoples test scripts, so I don't think we can do
>>>> this, sorry.
>>>
>>> I also think that this is not breaking any ABI. test_hush_if_test.py is
>>> around for a while to capture issues in this space and I can't see any
>>> single failure in connection to this change.
>>>
>>> If this accepted then we can add more tests like this
>>>      ('test 0x2000000 -gt 0x2000001', False),
>>>      ('test 0x2000000 -gt 0x2000000', False),
>>>      ('test 0x2000000 -gt 0x1ffffff', True),
>>>      ('test 2000000 -gt 0x1ffffff', False),
>>>      ('test 0x2000000 -gt 1ffffff', True),
>>>
>>>      ('test 0x2000000 -lt 1ffffff', False),
>>>      ('test 0x2000000 -eq 2000000', False),
>>>      ('test 0x2000000 -ne 2000000', True),
>>>
>>> where some of them are failing without this patch
>>> ... test_hush_if_test[test 0x2000000 -gt 0x1ffffff-True]
>>>
>>> ... test_hush_if_test[test 2000000 -gt 0x1ffffff-False]
>>>
>>> ... test_hush_if_test[test 0x2000000 -gt 1ffffff-True]
>>>
>>> ... test_hush_if_test[test 0x2000000 -lt 1ffffff-False]
>>>
>>
>> Any comment on this?
> 
> Sorry, yes, OK, we can take this then.  I should have this in my first
> batch of non-python general changes I grab.

But strtoul("010", NULL, 0) is 8 while strtoul("010", NULL, 10) is 10. 
Do we care for that change?

Regards,
Simon

  reply	other threads:[~2019-10-09 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 13:39 [U-Boot] [PATCH] cmd: avoid decimal conversion Michal Simek
2019-09-13 15:09 ` Tom Rini
2019-09-13 15:17   ` Michael Nazzareno Trimarchi
2019-09-19 13:28   ` Michal Simek
2019-10-08  8:48     ` Michal Simek
2019-10-09 16:26       ` Tom Rini
2019-10-09 17:28         ` Simon Goldschmidt [this message]
2019-10-10 10:46           ` Michal Simek
2019-10-10 10:49             ` Simon Goldschmidt
2019-10-12 20:23 ` Tom Rini

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=e8cec620-ca45-eb41-a7d2-b8b25ded760d@gmail.com \
    --to=simon.k.r.goldschmidt@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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