This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] xtensa: initialize call_abi in xtensa_tdep
- From: Pedro Alves <palves at redhat dot com>
- To: Max Filippov <jcmvbkbc at gmail dot com>, Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org, Maxim Grigoriev <maxim2405 at gmail dot com>, Woody LaRue <larue at cadence dot com>, Marc Gauthier <marc at cadence dot com>
- Date: Thu, 20 Aug 2015 15:13:28 +0100
- Subject: Re: [PATCH v2] xtensa: initialize call_abi in xtensa_tdep
- Authentication-results: sourceware.org; auth=none
- References: <1440075160-13310-1-git-send-email-jcmvbkbc at gmail dot com> <20150820130736 dot GF4571 at adacore dot com> <CAMo8BfK3AKap6eSV0j4hL1MypgH=D81jK1DAMEapKsUSOB3Jfw at mail dot gmail dot com>
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