From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61839 invoked by alias); 10 Jan 2017 19:14:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 61783 invoked by uid 89); 10 Jan 2017 19:14:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.1 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*f:sk:6fff44e, H*i:sk:6fff44e, H*MI:sk:6fff44e X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Jan 2017 19:14:37 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D3EF2C04B95E; Tue, 10 Jan 2017 19:14:36 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v0AJEBw6031188; Tue, 10 Jan 2017 14:14:30 -0500 Subject: Re: [PATCH, v2] Add command to erase all flash memory regions To: Luis Machado , Simon Marchi , "'gdb-patches@sourceware.org'" References: <1483988641-27277-1-git-send-email-lgustavo@codesourcery.com> <7353f551-64f3-9d8a-8e74-f85dd93b40d4@ericsson.com> <6fff44e6-74df-47ae-3cd2-2d3dca971f65@codesourcery.com> From: Pedro Alves Message-ID: Date: Tue, 10 Jan 2017 19:14:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <6fff44e6-74df-47ae-3cd2-2d3dca971f65@codesourcery.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-01/txt/msg00178.txt.bz2 >>>> +The output is a list of flash regions that have been erased, sorted by >>>> +address/size. >>> >>> What does it mean to be sorted by address/size? >>> >> >> It is actually an oversight. No sorting is done (the regions are shown >> in the same order as they are provided by the target). AFAICS, target_memory_map does a qsort on address. But it's probably better to not commit to any ordering. Thanks, Pedro Alves