From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15631 invoked by alias); 19 Jan 2011 21:50:55 -0000 Received: (qmail 15609 invoked by uid 22791); 19 Jan 2011 21:50:53 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 19 Jan 2011 21:50:45 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id p0JLogZr020912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Jan 2011 16:50:42 -0500 Received: from mesquite.lan (ovpn-113-42.phx2.redhat.com [10.3.113.42]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p0JLofBK021660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 19 Jan 2011 16:50:42 -0500 Date: Wed, 19 Jan 2011 21:55:00 -0000 From: Kevin Buettner To: gdb-patches@sourceware.org Cc: Paul Koning Subject: Re: [RFC] configure.tgt: Update mips*-*-* to use remote-mips.o Message-ID: <20110119145041.32229ce7@mesquite.lan> In-Reply-To: References: <20110119141436.2d8422fe@mesquite.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2011-01/txt/msg00417.txt.bz2 On Wed, 19 Jan 2011 16:20:50 -0500 Paul Koning wrote: > Shouldn't that just be for the MIPS based targets (if there still > are any left) that use this protocol? I want remote-mips.o to be enabled for the various mips*-elf targets. Would the patch be more palatable if I were to add a mips*-*-elf pattern for this case? > A lot of them probably just use the standard GDB remote protocol (I > know ours does -- NetBSD based). Keep in mind that adding remote-mips.o doesn't prevent the use of GDB's remote serial protocol. The "target remote" command will continue to work just as it always has. Also, I see the pattern "mips*-*-netbsd* | mips*-*-knetbsd*-gnu" in configure.tgt. So NetBSD wouldn't be affected by my change anyway. Kevin