From: Pedro Alves <palves@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>,
Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Maxim Grigoriev <maxim2405@gmail.com>,
Woody LaRue <larue@cadence.com>,
Marc Gauthier <marc@cadence.com>
Subject: Re: [PATCH v2] xtensa: initialize call_abi in xtensa_tdep
Date: Thu, 20 Aug 2015 14:13:00 -0000 [thread overview]
Message-ID: <55D5E088.3050807@redhat.com> (raw)
In-Reply-To: <CAMo8BfK3AKap6eSV0j4hL1MypgH=D81jK1DAMEapKsUSOB3Jfw@mail.gmail.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
next prev parent reply other threads:[~2015-08-20 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 12:53 Max Filippov
2015-08-20 13:07 ` Joel Brobecker
2015-08-20 13:14 ` [RFC] " Joel Brobecker
2015-08-20 13:44 ` Max Filippov
2015-08-20 13:37 ` Max Filippov
2015-08-20 14:13 ` Pedro Alves [this message]
2015-08-20 20:30 ` Marc Gauthier
2015-08-21 9:49 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D5E088.3050807@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jcmvbkbc@gmail.com \
--cc=larue@cadence.com \
--cc=marc@cadence.com \
--cc=maxim2405@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox