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 v5 6/7] compile: New 'compile print'
Date: Fri, 15 May 2015 17:04:00 -0000 [thread overview]
Message-ID: <55562703.4060104@redhat.com> (raw)
In-Reply-To: <20150513201704.4051.40784.stgit@host1.jankratochvil.net>
A couple very minor nits below, and this is good to go.
On 05/13/2015 09:17 PM, Jan Kratochvil wrote:
> + if (TYPE_CODE (gdb_type) != TYPE_CODE_PTR)
> + error (_("Invalid type code %d of symbol \"%s\" "
> + "in compiled module \"%s\"."),
> + TYPE_CODE (gdb_type_from_ptr), COMPILE_I_EXPR_VAL,
> + objfile_name (objfile));
> +
> + switch (TYPE_CODE (gdb_type_from_ptr))
> + {
> + case TYPE_CODE_ARRAY:
> + retval = gdb_type_from_ptr;
> + gdb_type_from_ptr = TYPE_TARGET_TYPE (gdb_type_from_ptr);
> + break;
> + case TYPE_CODE_FUNC:
> + retval = gdb_type_from_ptr;
AFAIC, retval is always gdb_type_from_ptr, and could be
moved out of the switch.
> + break;
> + default:
> + error (_("Invalid type code %d of symbol \"%s\" "
> + "in compiled module \"%s\"."),
> + TYPE_CODE (gdb_type_from_ptr), COMPILE_I_EXPR_PTR_TYPE,
> + objfile_name (objfile));
> + }
> diff --git a/gdb/compile/compile-object-load.h b/gdb/compile/compile-object-load.h
> index f5e887d..3e0e45b 100644
> --- a/gdb/compile/compile-object-load.h
> +++ b/gdb/compile/compile-object-load.h
> @@ -37,6 +37,14 @@ struct compile_module
>
> /* User data for SCOPE in use. */
> void *scope_data;
> +
> + /* Inferior parameter out value address or NULL if the inferior function does not
> + have one. */
Line too long, I think. Also, "NULL if the inferior function does not
have one" looks like a copy/paste, given this is not a pointer
variable. I'd swap around the fields, and write:
/* Inferior parameter out value type or NULL if the inferior function does not
have one. */
struct type *out_value_type;
/* If the inferior function has an out value, this is its address. */
CORE_ADDR out_value_addr;
> + CORE_ADDR out_value_addr;
> +
> + /* Inferior parameter out value type or NULL if the inferior function does not
> + have one. */
> + struct type *out_value_type;
> };
>
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-05-15 17:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:16 [PATCH v5 0/7] compile: compile print (&unmap) Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 2/7] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-05-16 12:27 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 3/7] compile: Distribute scope, add scope_data Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:39 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 4/7] compile: Use -Wall, not -w Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:43 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 1/7] compile: Add one debug message Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:19 ` [commit] " Jan Kratochvil
2015-05-16 13:09 ` [patch] compile: gdb_stdout -> gdb_stdlog [compile: Add one debug message] Jan Kratochvil
2015-05-19 11:47 ` Pedro Alves
2015-05-19 12:28 ` [commit] " Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 5/7] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-05-15 16:51 ` Pedro Alves
2015-05-16 12:45 ` [commit] " Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 7/7] RFC only: compile: Use also inferior munmap Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 6/7] compile: New 'compile print' Jan Kratochvil
2015-05-15 17:04 ` Pedro Alves [this message]
2015-05-16 12:58 ` [commit] " Jan Kratochvil
2015-05-16 13:39 ` [commit#2] " Jan Kratochvil
2015-05-16 14:25 ` [commit] " Patrick Palka
2015-05-16 14:39 ` [obv] " 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=55562703.4060104@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