From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9498 invoked by alias); 15 Feb 2011 18:48:40 -0000 Received: (qmail 9481 invoked by uid 22791); 15 Feb 2011 18:48:39 -0000 X-SWARE-Spam-Status: No, hits=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Feb 2011 18:48:35 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p1FImXOh016582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Feb 2011 13:48:33 -0500 Received: from anchor.twiddle.home (ovpn-113-82.phx2.redhat.com [10.3.113.82]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p1FImWtI000478; Tue, 15 Feb 2011 13:48:32 -0500 Message-ID: <4D5ACA80.2090005@redhat.com> Date: Tue, 15 Feb 2011 18:48:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 MIME-Version: 1.0 To: Anitha Boyapati CC: gdb@sourceware.org, binutils@sourceware.org Subject: Re: Testing Call frame information in .debug_frame section References: <4D5ABAB2.2000405@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00180.txt.bz2 On 02/15/2011 10:09 AM, Anitha Boyapati wrote: > I am a little confused here. I was under the impression that changes > to GCC files alone would suffice. I am missing something here. Are the > above mentioned changes required for assembling CFI information in > assembly files in binutils? GCC *can* produce cfi information by itself without assembler help, but can produce slightly more compact cfi information *with* help. In addition, with assembler support it's easy to write cfi info to go along with hand-written assembly. r~