From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21945 invoked by alias); 24 Jun 2006 02:26:27 -0000 Received: (qmail 21931 invoked by uid 22791); 24 Jun 2006 02:26:26 -0000 X-Spam-Check-By: sourceware.org Received: from shell4.bayarea.net (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 24 Jun 2006 02:26:24 +0000 Received: from [192.168.20.7] (209-128-106-254.bayarea.net [209.128.106.254]) (authenticated bits=0) by shell4.bayarea.net (8.13.6/8.13.6) with ESMTP id k5O2QMg5022023 for ; Fri, 23 Jun 2006 19:26:22 -0700 Message-ID: <449CA2CE.3020100@eagercon.com> Date: Sat, 24 Jun 2006 02:57:00 -0000 From: Michael Eager User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: PowerPC 405 support Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00198.txt.bz2 I was looking at adding support to GDB for a variant of the PPC 405. This variant has several added instructions but is otherwise the same, i.e., has the same registers, etc. I thought I'd add a processor type named Xppc405 or ppc405X for this variant. Then I noticed that the 405 is really not supported as a variant, but the 403 is, and that the 403 has extensions (and at least one hack) for the 405. There are opcodes defined for PPC405, but this symbol is aliased to PPC403. It looks pretty straight-forward to create a ppc405 variant and unalias it from the ppc403. Then create a ppc405X variant which builds on the ppc405. Any reason not to do this? Alternately I could (a) add the variant's instructions to the existing PPC405 definition and leave that as an alias for the PPC403. That would be quick, but seems dirty. BTW, does anyone have documentation on the PPC403? I can't find any online and if I do unalias PPC405 from PPC403, I'd like to make sure that the opcodes labeled PPC405 are really only in the 405, and not also in the 403. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077