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 7/9] compile: New 'compile print'
Date: Wed, 29 Apr 2015 15:53:00 -0000 [thread overview]
Message-ID: <5540FD9E.1020005@redhat.com> (raw)
In-Reply-To: <20150411194418.29128.3411.stgit@host1.jankratochvil.net>
On 04/11/2015 08:44 PM, Jan Kratochvil wrote:
> + case COMPILE_I_PRINT_ADDRESS_SCOPE:
> + case COMPILE_I_PRINT_VALUE_SCOPE:
> + fputs_unfiltered ("#include <string.h>\n"
OOC, why do we need the include?
> + "void "
> + GCC_FE_WRAPPER_FUNCTION
> + " (struct "
> + COMPILE_I_SIMPLE_REGISTER_STRUCT_TAG
> + " *"
> + COMPILE_I_SIMPLE_REGISTER_ARG_NAME
> + ", "
> + COMPILE_I_PRINT_OUT_ARG_TYPE
> + " "
> + COMPILE_I_PRINT_OUT_ARG
> + ") {\n",
> + buf);
> + break;
> +
> case COMPILE_I_RAW_SCOPE:
> break;
> default:
> @@ -354,6 +355,114 @@ copy_sections (bfd *abfd, asection *sect, void *data)
> do_cleanups (cleanups);
> }
>
> +/* Fetch the type of COMPILE_I_EXPR_PTR_TYPE and COMPILE_I_EXPR_VAL
> + symbols in OBJFILE so we can calculate how much memory to allocate
> + for the out parameter. This avoids needing a malloc in the generated
> + code. Throw an error if anything fails.
> + Set *OUT_VALUE_TAKE_ADDRESSP depending whether inferior code should
> + copy COMPILE_I_EXPR_VAL or its address - this depends on __auto_type
> + array-to-pointer type conversion of COMPILE_I_EXPR_VAL, as detected
> + by COMPILE_I_EXPR_PTR_TYPE preserving the array type. */
This comment seems a bit stale. At least, I don't see an
OUT_VALUE_TAKE_ADDRESSP parameter.
> +
> +static struct type *
> +get_out_value_type (struct symbol *func_sym, struct objfile *objfile,
> + enum compile_i_scope_types scope)
> +{
> + struct symbol *gdb_ptr_type_sym, *gdb_val_sym;
> + struct type *gdb_ptr_type, *gdb_type_from_ptr, *gdb_type, *retval;
> + const struct block *block;
> + const struct blockvector *bv;
> + int nblocks = 0;
> + int block_loop = 0;
Otherwise this looks reasonable to me.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-04-29 15:49 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
2015-04-11 19:44 ` [PATCH v3 7/9] compile: New 'compile print' Jan Kratochvil
2015-04-29 15:53 ` Pedro Alves [this message]
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 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 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 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=5540FD9E.1020005@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