From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72894 invoked by alias); 28 Nov 2018 15:59:29 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 72875 invoked by uid 89); 28 Nov 2018 15:59:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy= X-HELO: nikam.ms.mff.cuni.cz Received: from nikam.ms.mff.cuni.cz (HELO nikam.ms.mff.cuni.cz) (195.113.20.16) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Nov 2018 15:59:27 +0000 Received: by nikam.ms.mff.cuni.cz (Postfix, from userid 16202) id 7D6B028E702; Wed, 28 Nov 2018 16:59:25 +0100 (CET) Date: Wed, 28 Nov 2018 15:59:00 -0000 From: Jan Hubicka To: Andi Kleen Cc: Andi Kleen , gcc-patches@gcc.gnu.org Subject: Re: [PING^3] Re: [PATCH 1/3] Support instrumenting returns of instrumented functions Message-ID: <20181128155925.scunfvykz6ipknti@kam.mff.cuni.cz> References: <20181105000221.32180-1-andi@firstfloor.org> <87r2fvmr4j.fsf@linux.intel.com> <87y39uw4cf.fsf_-_@linux.intel.com> <87sgzuyx5z.fsf_-_@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sgzuyx5z.fsf_-_@linux.intel.com> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-11/txt/msg02316.txt.bz2 Hi, I wonder how __return_loc sections work. In general it would be nice to avoid direct output of assembler code in favour of adding instructions to rtl stream which should be possible to insert the call and return. __return_loc seems harder, also I wonder if it makes unwind information possible? Honza