From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24870 invoked by alias); 17 May 2013 23:10:17 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 24856 invoked by uid 89); 17 May 2013 23:10:17 -0000 X-Spam-SWARE-Status: No, score=-7.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 17 May 2013 23:10:16 +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 r4HNAF4I017759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 May 2013 19:10:15 -0400 Received: from mesquite.lan (ovpn-113-81.phx2.redhat.com [10.3.113.81]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r4HNAEHp005690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 17 May 2013 19:10:15 -0400 Date: Fri, 17 May 2013 23:10:00 -0000 From: Kevin Buettner To: gdb-patches@sourceware.org Subject: Re: [WIP] TI msp430 CIO support Message-ID: <20130517161013.558bd131@mesquite.lan> In-Reply-To: <201305171744.00275.vapier@gentoo.org> References: <20130516212358.23f3bcdb@mesquite.lan> <201305171744.00275.vapier@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2013-05/txt/msg00707.txt.bz2 On Fri, 17 May 2013 17:43:59 -0400 Mike Frysinger wrote: > you could have the simulator detect the case when it's running standalone > (i.e. not via gdb) and patch the symbols to run a custom insn. maybe hijack > an opcode that doesn't map to a valid insn and then when your sim hits that, > see if it's a known cio point. if it isn't, throw an exception like normal, > else let the simulator process the cio operation itself. > > you could even have this code run when doing a simulation via gdb and it'll > "just work". but you might want to keep the behavior in that case the same as > if you were running it on real hardware. We actually do have minimal support in the simulator that's used when the sim is not connected to the debugger. Only "write" is supported. This is just enough to run the tests. We could probably turn this back on when the sim is used via GDB too. If you look at the sim patch, search for "msp430_cio". Kevin