From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6336 invoked by alias); 6 May 2003 12:34:34 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6329 invoked from network); 6 May 2003 12:34:33 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 6 May 2003 12:34:33 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h46CYXH19953 for ; Tue, 6 May 2003 08:34:33 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h46CYXI12487 for ; Tue, 6 May 2003 08:34:33 -0400 Received: from localhost.localdomain (vpn50-18.rdu.redhat.com [172.16.50.18]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h46CYXP18483 for ; Tue, 6 May 2003 08:34:33 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h46CYRo24518 for gdb@sources.redhat.com; Tue, 6 May 2003 05:34:27 -0700 Date: Tue, 06 May 2003 12:34:00 -0000 From: Kevin Buettner Message-Id: <1030506123427.ZM24517@localhost.localdomain> To: gdb@sources.redhat.com Subject: LSI 33k ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg00068.txt.bz2 Does anyone know anything about the LSI 33k? Okay, more specifically, did support for this core ever actually work in GDB? In mips-tdep.c, I see the following: /* Names of LSI 33k registers. */ char *mips_lsi33k_reg_names[] = { "epc", "hi", "lo", "sr", "cause","badvaddr", "dcic", "bpc", "bda", "", "", "", "", "", "", "", "", "", "", "", "", "", ... With the exception of IRIX, the first line for all of the other regname sets look like this: "sr", "lo", "hi", "bad", "cause","pc", I'm not concerned about IRIX, because BADVADDR_REGNUM, CAUSE_REGNUM, PC_REGNUM, etc. are redefined in the appropriate tm-*.h file. The LSI 33k rearranges these registers, apparently even the PC_REGNUM value, but nowhere do I see a PC_REGNUM definition that's specific to the LSI 33k. This is bad because if the LSI 33k registers are really laid out as indicated by lsi33_reg_names[], then there's no way that GDB is actually obtaining the correct PC value whenever it uses PC_REGNUM. (It'll be using the "baddvaddr" value...) I thought for a while that perhaps the LSI 33k was simply bit-rotted, but after doing some digging in the old Cygnus CVS repository, I don't see how it could have ever worked. Does anyone know? Kevin