From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH v3 2/9] compile: Distribute scope, add scope_data
Date: Wed, 29 Apr 2015 15:44:00 -0000 [thread overview]
Message-ID: <5540FC3F.5050203@redhat.com> (raw)
In-Reply-To: <20150411194341.29128.87444.stgit@host1.jankratochvil.net>
On 04/11/2015 08:43 PM, Jan Kratochvil wrote:
> Provide a way to access current 'scope' during struct the do_module_cleanup
"struct" ?
> stage and associate more data with it.
>
> It should be all sub-classed but AFAIK GDB does not require C++ compiler yet.
>
Right, it does not.
> gdb/ChangeLog
> 2015-04-06 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * cli/cli-script.c (execute_control_command): Update
> eval_compile_command caller.
> * compile/compile-object-load.c (compile_object_load): Add parameters
> scope and scope_data. Set them.
> * compile/compile-object-load.h (struct compile_module): Add fields
> scope and scope_data.
> (compile_object_load): Add parameters scope and scope_data.
> * compile/compile-object-run.c (struct do_module_cleanup): Add fields
> scope and scope_data.
> (compile_object_run): Propage the fields scope and scope_data.
Propagate.
> * compile/compile.c (compile_file_command, compile_code_command):
> Update eval_compile_command callers.
> (eval_compile_command): Add parameter scope_data. Pass it plus scope.
> * compile/compile.h (eval_compile_command): Add parameter scope_data.
> * defs.h (struct command_line): Add field
>
> extern struct compile_module *compile_object_load (const char *object_file,
> - const char *source_file);
> + const char *source_file,
> + enum compile_i_scope_types scope,
> + void *scope_data);
If the line overflows, then break before the (, and indent with two spaces.
See e.g., extension.h:
extern const struct extension_language_defn *get_ext_lang_defn
(enum extension_language lang);
Otherwise OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-04-29 15:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 19:43 [PATCH v3 0/9] compile: compile print&printf Jan Kratochvil
2015-04-11 19:43 ` [PATCH v3 3/9] Code cleanup: compile: Constify some parameters Jan Kratochvil
2015-04-29 15:47 ` Pedro Alves
2015-05-06 18:58 ` [commit] " Jan Kratochvil
2015-04-11 19:43 ` [PATCH v3 1/9] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-04-29 15:44 ` Pedro Alves
2015-04-30 0:24 ` Jan Kratochvil
2015-04-11 19:43 ` [PATCH v3 2/9] compile: Distribute scope, add scope_data Jan Kratochvil
2015-04-29 15:44 ` Pedro Alves [this message]
2015-04-11 19:44 ` [PATCH v3 7/9] compile: New 'compile print' Jan Kratochvil
2015-04-29 15:53 ` Pedro Alves
2015-05-03 14:06 ` Jan Kratochvil
2015-05-06 10:22 ` Pedro Alves
2015-05-06 12:23 ` Jan Kratochvil
2015-05-06 14:11 ` Pedro Alves
2015-05-06 19:18 ` Jan Kratochvil
2015-05-15 16:35 ` Pedro Alves
2015-04-11 19:44 ` [PATCH v3 6/9] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-04-29 15:52 ` Pedro Alves
2015-04-11 19:44 ` [PATCH v3 4/9] compile: Support relocation to GNU-IFUNCs Jan Kratochvil
2015-04-29 15:48 ` Pedro Alves
2015-05-06 19:00 ` [commit] " Jan Kratochvil
2015-04-11 19:44 ` [PATCH v3 9/9] compile: compile printf: gdbserver support Jan Kratochvil
2015-04-26 9:33 ` Jan Kratochvil
2015-04-29 18:19 ` Pedro Alves
2015-05-03 14:06 ` Jan Kratochvil
2015-05-06 10:22 ` Pedro Alves
2015-04-29 16:12 ` Pedro Alves
2015-04-11 19:44 ` [PATCH v3 8/9] compile: New compile printf Jan Kratochvil
2015-04-29 15:54 ` Pedro Alves
2015-05-03 14:06 ` Jan Kratochvil
2015-05-06 10:22 ` Pedro Alves
2015-05-06 11:30 ` Jan Kratochvil
2015-05-06 11:47 ` Pedro Alves
2015-04-11 19:44 ` [PATCH v3 5/9] compile: Use -Wall, not -w Jan Kratochvil
2015-04-29 15:49 ` Pedro Alves
2015-05-03 14:05 ` Jan Kratochvil
2015-05-06 10:21 ` 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=5540FC3F.5050203@redhat.com \
--to=palves@redhat.com \
--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