From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36043 invoked by alias); 8 May 2017 08:13:34 -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 36017 invoked by uid 89); 8 May 2017 08:13:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-10.9 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=necessity, transfer, Transfer X-HELO: mga03.intel.com Received: from mga03.intel.com (HELO mga03.intel.com) (134.134.136.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 08 May 2017 08:13:31 +0000 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2017 01:13:32 -0700 X-ExtLoop1: 1 Received: from irvmail001.ir.intel.com ([163.33.26.43]) by fmsmga002.fm.intel.com with ESMTP; 08 May 2017 01:13:31 -0700 Received: from ulvlx001.iul.intel.com (ulvlx001.iul.intel.com [172.28.207.17]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id v488DUiJ018472; Mon, 8 May 2017 09:13:31 +0100 Received: from ulvlx001.iul.intel.com (localhost [127.0.0.1]) by ulvlx001.iul.intel.com with ESMTP id v488DUhP004964; Mon, 8 May 2017 10:13:30 +0200 Received: (from twiederh@localhost) by ulvlx001.iul.intel.com with œ id v488DUPA004960; Mon, 8 May 2017 10:13:30 +0200 From: Tim Wiederhake To: gdb-patches@sourceware.org Cc: markus.t.metzger@intel.com Subject: [PATCH v2 00/11] btrace: Turn linked list of function call segments into vector Date: Mon, 08 May 2017 08:13:00 -0000 Message-Id: <1494231185-4709-1-git-send-email-tim.wiederhake@intel.com> X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00168.txt.bz2 Hi all, this series removes the extra list of btrace function call segments in struct btrace_thread_info. To achieve this, the doubly linked list of function call segments in struct btrace_thread_info is replaced by a (GDB) vector. In some instances, struct btrace_thread_info is initialized by memset'ing it to 0x00, so we can't use std::vector (yet). V1 of this series can be found here: https://sourceware.org/ml/gdb-patches/2017-02/msg00482.html The patches are differently ordered in comparison to V1, removing the necessity of the "big squash". Regards, Tim Tim Wiederhake (11): btrace: Transfer ownership of pointers. btrace: Add btinfo to instruction interator. btrace: Use function segment index in call iterator. btrace: Use function segment index in insn iterator. btrace: Remove constant arguments. btrace: Remove struct btrace_thread_info::{begin,end}. btrace: Replace struct btrace_thread_info::up. btrace: Remove struct btrace_thread_info::flow. btrace: Replace struct btrace_thread_info::segment. btrace: Remove bfun_s vector. btrace: Store function segments as objects. gdb/btrace.c | 852 +++++++++++++++++++++--------------------- gdb/btrace.h | 62 ++- gdb/python/py-record-btrace.c | 12 +- gdb/record-btrace.c | 32 +- 4 files changed, 472 insertions(+), 486 deletions(-) -- 2.7.4