From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19869 invoked by alias); 3 Jan 2014 18:07:50 -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 19855 invoked by uid 89); 3 Jan 2014 18:07:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: saffron.mail.virginia.edu Received: from saffron.mail.Virginia.EDU (HELO saffron.mail.virginia.edu) (128.143.2.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 03 Jan 2014 18:07:46 +0000 Received: from localhost (localhost [127.0.0.1]) by saffron.mail.virginia.edu (Postfix) with ESMTP id E4BEC17A1AA for ; Fri, 3 Jan 2014 13:07:44 -0500 (EST) Received: from saffron.mail.virginia.edu ([127.0.0.1]) by localhost (saffron-f.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5+Ac+AdKuD0 for ; Fri, 3 Jan 2014 13:07:44 -0500 (EST) Received: from iron1.mail.virginia.edu (iron1-s.mail.virginia.edu [10.250.200.226]) by saffron.mail.virginia.edu (Postfix) with ESMTP id 3A20B17A191 for ; Fri, 3 Jan 2014 13:07:43 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnUHABT8xlIK+siS/2dsb2JhbABYug2EOHSCZDYKPRYYAwIBAgFYCAEBx0KDaRePK4QhBIlDlRmEFYsFgUok X-Sender-IP: 10.250.200.146 Received: from cod-s.mail.virginia.edu (HELO mail.virginia.edu) ([10.250.200.146]) by iron1.mail.virginia.edu with ESMTP; 03 Jan 2014 13:07:43 -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 55436980 for gcc-help@gcc.gnu.org; Fri, 03 Jan 2014 13:07:43 -0500 Message-ID: <52C6FC6D.5020001@virginia.edu> Date: Fri, 03 Jan 2014 18:07:00 -0000 From: Michele Co User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Help with gathering information on compiler-generated temporary variables Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00004.txt.bz2 I am new to developing in gcc, so I am seeking help on gcc-help. If this message belongs on a different list, please advise. I am working with the gcc 4.4.3 source tree and am looking for a way to gather for later use (in human readable format) any information on compiler-generated temporaries (variables or values held in registers, locations, offsets, sizes). I have perused the available gcc documentation and searched the gcc-help and gcc mailing list archives but have not found any threads related to this topic. My original approach has been to modify one of gcc's debugger output modules (dbxout) to output new STABS entries, but I have been having difficulty keeping track of the compiler-generated temporaries through the various compiler passes. I seem to lose track of them after the GIMPLE pass, possibly due to my lack of understanding of how the information flows to the various tree representations. Any advice or pointers to helpful documentation/forums is welcome. Thanks, Michele