From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69724 invoked by alias); 20 Aug 2015 14:13:34 -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 69715 invoked by uid 89); 20 Aug 2015 14:13:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 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; Thu, 20 Aug 2015 14:13:32 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 72920A2C32; Thu, 20 Aug 2015 14:13:31 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t7KEDSPr012623; Thu, 20 Aug 2015 10:13:29 -0400 Message-ID: <55D5E088.3050807@redhat.com> Date: Thu, 20 Aug 2015 14:13:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Max Filippov , Joel Brobecker CC: gdb-patches@sourceware.org, Maxim Grigoriev , Woody LaRue , Marc Gauthier Subject: Re: [PATCH v2] xtensa: initialize call_abi in xtensa_tdep References: <1440075160-13310-1-git-send-email-jcmvbkbc@gmail.com> <20150820130736.GF4571@adacore.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-08/txt/msg00548.txt.bz2 On 08/20/2015 02:37 PM, Max Filippov wrote: > Actually it's as simple as unpacking a tarball to the source directory, > and we have it automated in the environments that build toolchains, > like the Buildroot or the crosstool-NG. > > The idea behind this is the following: Xtensa core is configurable, a lot > of its properties may be changed. Nobody even try to test all possible > combinations of configuration options and nobody really cares how many > Xtensa core configurations exist, people that generate Xtensa core > only care about their particular core. When they generate it they get > all the files that need to be changed in the toolchain, they apply them > and they get the toolchain for their particular core. How about making the configuration generator tool output some data file that gdb would source? Thanks, Pedro Alves