From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4515 invoked by alias); 29 Nov 2011 21:18:13 -0000 Received: (qmail 4507 invoked by uid 22791); 29 Nov 2011 21:18:13 -0000 X-SWARE-Spam-Status: No, hits=-7.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS 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; Tue, 29 Nov 2011 21:17:39 +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 pATLHaDb000760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2011 16:17:36 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pATLHaq6025658; Tue, 29 Nov 2011 16:17:36 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pATLHY9L016997; Tue, 29 Nov 2011 16:17:35 -0500 From: Tom Tromey To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [RFC/WIP PATCH 03/14] Flip to set target-async on by default References: <20111128153742.17761.21459.stgit@localhost6.localdomain6> <20111128153910.17761.37341.stgit@localhost6.localdomain6> Date: Tue, 29 Nov 2011 21:18:00 -0000 In-Reply-To: <20111128153910.17761.37341.stgit@localhost6.localdomain6> (Pedro Alves's message of "Mon, 28 Nov 2011 15:39:10 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-11/txt/msg00830.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> This flips "set target-async" to default to on. I see no failures Pedro> left with this on x86_64-linux, and there used to be none either Pedro> against gdbserver, but I haven't tried recently. One thing left to Pedro> decide is what to do with MI. If the frontend never flips async Pedro> explicitly, should we bother to emulate sync MI output, or can we Pedro> expect that all frontends can and should cope with async on by default Pedro> by now? First, I want us to make target-async default to on. I have a few other defaults I'd like to flip, too. For the MI part, I think we should reach out to the "main" MI consumers out there -- and by "main" I just mean ones that we know of and that seem to be maintained -- and ask. (It seems like it would be good to have some open channel for doing this more regularly.) Actually, come to think of it, instead of asking, we should probably just announce the change and see what kind of push-back we get. In the extreme we can make the next release "8.0" as a way of advertising that we're making bigger changes. Tom