From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] ABI: Add abi checking utility Date: Fri, 27 Feb 2015 14:55:55 +0100 Message-ID: <3572172.j6x246F0TI@xps13> References: <1422652596-12777-1-git-send-email-nhorman@tuxdriver.com> <1422901106-20734-1-git-send-email-nhorman@tuxdriver.com> <20150227134837.GB1611@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Neil Horman Return-path: In-Reply-To: <20150227134837.GB1611-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Neil, 2015-02-27 08:48, Neil Horman: > On Mon, Feb 02, 2015 at 01:18:26PM -0500, Neil Horman wrote: > > There was a request for an abi validation utiltyfor the ongoing ABI stability > > work. As it turns out there is a abi compliance checker in development that > > seems to be under active development and provides fairly detailed ABI compliance > > reports. Its not yet intellegent enough to understand symbol versioning, but it > > does provide the ability to identify symbols which have changed between > > releases, along with details of the change, and offers develoeprs the > > opportunity to identify which symbols then need versioning and validation for a > > given update via manaul testing. > > > > This script automates the use of the compliance checker between two arbitrarily > > specified tags within the dpdk tree. To execute enter the $RTE_SDK directory > > and run: > > > > ./scripts/validate_abi.sh $GIT_TAG1 $GIT_TAG2 $CONFIG > > > > where $GIT_TAG1 and 2 are git tags and $CONFIG is a config specification > > suitable for passing as the T= variable in the make config command. > > > > Signed-off-by: Neil Horman > > Whats the disposition of this, I don't see it in the repository yet. I plan to review it carefully during next week. We can integrate this tool until end of March, that's why it was not the highest priority.