From: <Paul_Koning@Dell.com>
To: <jan.kratochvil@redhat.com>
Cc: <eliz@gnu.org>, <gdb-patches@sourceware.org>, <pmuldoon@redhat.com>
Subject: Re: [PATCH v2 7/9] compile: New 'compile print'
Date: Mon, 06 Apr 2015 18:00:00 -0000 [thread overview]
Message-ID: <0484210C-BBE9-4C64-8F51-7DC74ACF8F86@dell.com> (raw)
In-Reply-To: <20150406175250.GA314@host1.jankratochvil.net>
> On Apr 6, 2015, at 1:52 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
>
> On Mon, 06 Apr 2015 19:49:28 +0200, Paul_Koning@dell.com wrote:
>> where does it run? Presumably on the target.
>
> Yes.
>
>> Does it only work for native gdb?
>
> Yes.
>
>> Does it work with gdbserver?
>
> Yes.
>
>> It would be good to state the limitations and assumptions.
>
> I am not aware of any, there may be needed some target-specific support like
> for s390 gcc -m31 but in general it should work.
>
> I could pick some 10 years old discussion that NEWS file should not contain
> limitations, that those are just bugs for future ChangeLog entries.
I meant limitations such as “native only”. But given that it works across the board (give or take bugs) I agree that NEWS doesn’t need to say anything further.
>
>
>> 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.
paul
next prev parent reply other threads:[~2015-04-06 18:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 17:26 [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 3/9] Code cleanup: compile: Constify some parameters Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 2/9] compile: Distribute scope, add scope_data Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 4/9] compile: Support relocation to GNU-IFUNCs Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 1/9] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 8/9] compile: New compile printf Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 6/9] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 7/9] compile: New 'compile print' Jan Kratochvil
2015-04-06 17:41 ` Eli Zaretskii
2015-04-06 17:49 ` Paul_Koning
2015-04-06 17:52 ` Jan Kratochvil
2015-04-06 18:00 ` Paul_Koning [this message]
2015-04-08 20:03 ` Jan Kratochvil
2015-04-09 7:39 ` Eli Zaretskii
2015-04-09 17:40 ` [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print'] Jan Kratochvil
2015-04-09 18:12 ` Eli Zaretskii
2015-04-10 8:09 ` Jan Kratochvil
2015-04-10 8:31 ` Eli Zaretskii
2015-04-10 8:35 ` [commit] " Jan Kratochvil
2015-04-10 14:09 ` Paul_Koning
2015-04-08 20:12 ` [PATCH v2 7/9] compile: New 'compile print' Paul_Koning
2015-04-08 20:33 ` Jan Kratochvil
2015-04-06 18:47 ` Jan Kratochvil
2015-04-11 19:20 ` Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 5/9] compile: Use -Wall, not -w Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 9/9] compile: compile printf: gdbserver support Jan Kratochvil
2015-04-06 17:43 ` Eli Zaretskii
2015-04-11 19:23 ` Jan Kratochvil
2015-04-11 19:31 ` Eli Zaretskii
2015-04-11 19:46 ` obsolete: [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
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=0484210C-BBE9-4C64-8F51-7DC74ACF8F86@dell.com \
--to=paul_koning@dell.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).