From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5638 invoked by alias); 22 Jan 2014 19:36:48 -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 5624 invoked by uid 89); 22 Jan 2014 19:36:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: dill.mail.virginia.edu Received: from dill.mail.Virginia.EDU (HELO dill.mail.virginia.edu) (128.143.2.119) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 22 Jan 2014 19:36:47 +0000 Received: from localhost (localhost [127.0.0.1]) by dill.mail.virginia.edu (Postfix) with ESMTP id 98DD710A135 for ; Wed, 22 Jan 2014 14:36:45 -0500 (EST) Received: from dill.mail.virginia.edu ([127.0.0.1]) by localhost (dill-f.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZaX4foJjsyn for ; Wed, 22 Jan 2014 14:36:45 -0500 (EST) Received: from iron4.mail.virginia.edu (iron4-s.mail.virginia.edu [10.250.200.114]) by dill.mail.virginia.edu (Postfix) with ESMTP id 7454C10A0B0 for ; Wed, 22 Jan 2014 14:36:45 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvoHAKYc4FIK+siS/2dsb2JhbABbvGQOgwWBLXSCJQEBAQQ4QAEQCw4KCRYPCQMCAQIBRQYNAQcBAcZOhH8XjnwHhDgEiUeVIoQWiSqBXIFKJA X-Sender-IP: 10.250.200.146 Received: from cod-s.mail.virginia.edu (HELO mail.virginia.edu) ([10.250.200.146]) by iron4.mail.virginia.edu with ESMTP; 22 Jan 2014 14:36:45 -0500 Received: from [128.143.71.3] (account mc2zk@cms.mail.virginia.edu [128.143.71.3] verified) by cod.mail.virginia.edu (CommuniGate Pro SMTP 5.4.4) with ESMTPSA id 56421578; Wed, 22 Jan 2014 14:36:45 -0500 Message-ID: <52E01DCB.6030801@virginia.edu> Date: Wed, 22 Jan 2014 19:36:00 -0000 From: Michele Co User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Jonathan Wakely CC: gcc-help Subject: Re: Any way to output information on compiler-generated temporary variables in gcc? References: <52DD39FD.80708@virginia.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00084.txt.bz2 On 1/20/2014 10:55 AM, Jonathan Wakely wrote: > One of the -fdump-tree-xxx options might provide the information you > want, e.g. -fdump-tree-original I don't think debug info includes > temporaries that aren't named in the source, but I could be wrong. Hi Jonathan, Thank you very much for your pointer to the -fdump-tree-xxx options. I tried the -fdump-tree-all which seemed to dump all the available trees during the various passes. Is there any way that I can determine which tree is the "latest" tree? In other words, which is the tree that is the closest to the generated binary code? I noticed that the naming of the output files includes a 3-digit number. Is that number an indicator of how far along in the compilation that the tree was dumped? If there's some config/.opt file that I can refer to understand what has been done during each of the various tree dump versions, that information is welcome as well, as I'm unsure what some of the abbreviations mean, such as -fdump-tree-ch, -fdump-tree-dse, etc. --Michele