This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 7/9] compile: New 'compile print'
- From: <Paul_Koning at Dell dot com>
- To: <jan dot kratochvil at redhat dot com>
- Cc: <eliz at gnu dot org>, <gdb-patches at sourceware dot org>, <pmuldoon at redhat dot com>
- Date: Wed, 8 Apr 2015 20:11:58 +0000
- Subject: Re: [PATCH v2 7/9] compile: New 'compile print'
- Authentication-results: sourceware.org; auth=none
- References: <20150406172623 dot 31404 dot 58833 dot stgit at host1 dot jankratochvil dot net> <20150406172716 dot 31404 dot 8551 dot stgit at host1 dot jankratochvil dot net> <83bnj1jgsw dot fsf at gnu dot org> <021F612D-0E51-44ED-BA7F-894A8B51F5BF at dell dot com> <20150406175250 dot GA314 at host1 dot jankratochvil dot net> <0484210C-BBE9-4C64-8F51-7DC74ACF8F86 at dell dot com>
> On Apr 6, 2015, at 1:58 PM, paul_koning@dell.com wrote:
>
>
>> On Apr 6, 2015, at 1:52 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
>> ...
>>> Also, “the compiler” begs the question: which one, i.e., how is “the
>>> compiler” found?
>>
>> A complicated way, for non-native targets an appropriate cross-gcc should be
>> found.
>
> Ok. I would not expect that to be documented in NEWS, but it seems like it should be in gdb.texinfo or some similar spot. I have a whole pile of cross-compilers in various places; I would need to understand what the algorithm looks like to be able to ensure that the correct one is found.
A related question: what controls the compiler switches sent to the compiler for this operation? In some cases, specific switches may be needed to produce the correct flavor of code generation, say -msoft-float or -mabi=xyz.
paul