From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20914 invoked by alias); 18 Aug 2014 15:31:48 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 20865 invoked by uid 89); 18 Aug 2014 15:31:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 18 Aug 2014 15:31:44 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7IFVfqo019418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 18 Aug 2014 11:31:41 -0400 Received: from [10.36.7.155] (vpn1-7-155.ams2.redhat.com [10.36.7.155]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s7IFVQdI013393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 18 Aug 2014 11:31:40 -0400 Message-ID: <53F21C4B.4000109@redhat.com> Date: Mon, 18 Aug 2014 15:31:00 -0000 From: Nicholas Clifton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Tristan Gingold , Joel Brobecker CC: "binutils@sourceware.org" , gdb@sourceware.org Subject: Synchronizing Binutils and GDB releases Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00064.txt.bz2 Hi Tristan, Hi Joel, What do you think to the idea of synchronizing GDB and BINUTILS releases ? The idea was raised at this year's GNU Tool's Cauldron. It would help users who manage combined toolchain sources. Currently if they want to create a combined tree of specific releases of the gcc, gdb and binutils they have to choose which version of the BFD library to use. But if they find a bug and want to check in a fix, they have to remember that there are actually two versions of the BFD sources to patch. Multiply this by a number of different GDB/BINUTILS release combintations and this becomes a maintenance headache. If we had a combined release there would be only one branch in the git repository and things would be a lot simpler. We could even extend this idea by arranging for the release to happen slightly before each GCC release. Then GCC version X could could say that it works best with GDB/BINUTILS version Y. Cheers Nick