From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11414 invoked by alias); 22 Sep 2006 19:11:03 -0000 Received: (qmail 11402 invoked by uid 22791); 22 Sep 2006 19:11:02 -0000 X-Spam-Check-By: sourceware.org Received: from hq.tensilica.com (HELO mailapp.tensilica.com) (65.205.227.29) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 22 Sep 2006 19:11:01 +0000 Received: from localhost ([127.0.0.1] ident=amavis) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1GQqQN-0008Mu-28; Fri, 22 Sep 2006 12:10:59 -0700 Received: from mailapp.tensilica.com ([127.0.0.1]) by localhost (mailapp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31500-03; Fri, 22 Sep 2006 12:10:58 -0700 (PDT) Received: from maxim_fc3.hq.tensilica.com ([192.168.11.68]) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1GQqQM-0008Mm-Jx; Fri, 22 Sep 2006 12:10:58 -0700 Message-ID: <45143542.5060206@hq.tensilica.com> Date: Fri, 22 Sep 2006 19:11:00 -0000 From: Maxim Grigoriev User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Michael Snyder CC: Maxim Grigoriev , gdb-patches@sources.redhat.com, Bob Wilson , chris Zankel Subject: Re: Xtensa port References: <45142A88.7000805@hq.tensilica.com> <1158951165.22863.82.camel@localhost.localdomain> In-Reply-To: <1158951165.22863.82.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00148.txt.bz2 Michael, Thanks much for the quick response. > At a quick first glance, it looks pretty good. > Do you have a copyright assignment on file > Once in a while, Daniel Jacobowitz mentioned that he has all the necessary paper work for Xtensa port. I hope it still true. > One question -- is there a reason for splitting xtensa-config.c > into a separate file? Not necessarily a problem, but it seems > to be mostly stuff that would traditionally go in the xxx-tdep.c > file (such as the struct gdbarch_tdep object). > It's because Xtensa is all about configurability. Historically, Tensilica uses a special configuration called FSF for all our FSF submissions. It's been used for Xtensa GCC and BFD work. Now, I'm trying to use it for GDB. So when we have to deal with a different configuration of the Xtensa processor all we need is to update xtensa-config.c file. -- Maxim