[PATCH v2] xtensa: initialize call_abi in xtensa_tdep

[Pedro Alves]

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