From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16836 invoked by alias); 11 Aug 2014 19:15:31 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 16805 invoked by uid 89); 11 Aug 2014 19:15:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mailout12.t-online.de Received: from mailout12.t-online.de (HELO mailout12.t-online.de) (194.25.134.22) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 11 Aug 2014 19:15:26 +0000 Received: from fwd07.aul.t-online.de (fwd07.aul.t-online.de [172.20.27.150]) by mailout12.t-online.de (Postfix) with SMTP id 92C58ECF5F; Mon, 11 Aug 2014 21:15:22 +0200 (CEST) Received: from [192.168.0.103] (Thn6VkZaohTTcDFxhJANR6NfKo58xiitinFB4JD6jgwPQAuYagat5ZyOHM5Ukh8ggQ@[87.155.253.53]) by fwd07.t-online.de with (TLSv1:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XGv3r-0d4JpA0; Mon, 11 Aug 2014 21:15:15 +0200 Message-ID: <1407784512.16524.62.camel@yam-132-YW-E178-FTW> Subject: Re: g++ compiler generated copy constructor From: Oleg Endo To: navin p Cc: gcc-help@gcc.gnu.org Date: Mon, 11 Aug 2014 19:15:00 -0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00095.txt.bz2 Hello, On Mon, 2014-08-11 at 23:24 +0530, navin p wrote: > Hi, > Is there any way i can see the compiler generated copy constructor > and default constructor/destructor as a .cpp file instead of assembly > ? Any flags to g++, > Since you haven't specified what kind of information you want to have about the generated functions, one can only guess. Maybe looking at some of the tree/RTL dumps (try option -fdump-tree-all-details or -fdump-rtl-all-details see https://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging-Options for details) might contain the information you're looking for. Notice however, that the generated functions might get optimized away completely after they have been inlined into the caller. Cheers, Oleg