From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22398 invoked by alias); 16 Jun 2003 12:49:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22254 invoked from network); 16 Jun 2003 12:49:19 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 16 Jun 2003 12:49:19 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 94D3E2B5F; Mon, 16 Jun 2003 08:49:16 -0400 (EDT) Message-ID: <3EEDBCCC.6050609@redhat.com> Date: Mon, 16 Jun 2003 12:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kei Sakamoto Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] multi-arching m32r References: <016301c31610$aafb4e70$5169910a@KEI> <3EBC1157.8070601@redhat.com> <028b01c333f2$d2a61db0$5169910a@KEI> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00526.txt.bz2 > Andrew, > I sent back a Copyright Assignment form to FSF today. I also > built multi-arched m32r-gdb with current GDB snapshot. It works > fine. Great! > But my m32r-tdep.c still contains many functions which are > identified as "deprecated". You mentioned new m32r files should > not contains no deprecated code. But it seems that most of > architecutures' files, except d10v and i386, contains deprecated > code. d10v, i386, x86-64, avr, alpha > Can I post new m32r files with deprecated functions and > take care of their deprecated code later? Once the assignment is in place, they can certainly be posted. Unfortunatly, they won't be accepted for the mainline until they pass the `new architecture' acceptance criteria. One thing to consider (again once an assignment is in place) is creating a branch and working on that. > It is pretty > difficult to remove all deprecated code from m32r files > beacuse there are not much examples and documents about the > new frame and inferior function call mechanism now. Andrew