From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: [commit] [PATCH v5 6/7] compile: New 'compile print'
Date: Sat, 16 May 2015 12:58:00 -0000 [thread overview]
Message-ID: <20150516125814.GE9862@host1.jankratochvil.net> (raw)
In-Reply-To: <55562703.4060104@redhat.com>
On Fri, 15 May 2015 19:04:03 +0200, Pedro Alves wrote:
> 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.
It was written this way as it has semantical logic - how the type is
determined depends on TYPE_CODE_* of that object. Just accidentally in this
case it is the same. I do not do performance micro-optimizations which
compiler will do anyway. But I have changed it.
> > + /* Inferior parameter out value address or NULL if the inferior function does not
> > + have one. */
>
> Line too long, I think.
Yes, fixed. (Not discussing the 72 vs. 78 or 80 or which width of comments
rule.)
> Also, "NULL if the inferior function does not have one" looks like
> a copy/paste, given this is not a pointer variable.
It is "inferior NULL", so I find that "NULL" valid there.
> 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;
Done although I have added line "Otherwise it is zero." there:
+ /* 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.
+ Otherwise it is zero. */
+ CORE_ADDR out_value_addr;
Without that line 'out_value_addr' would be unspecified if out_value_type is
NULL which does not correspond to the current code.
Checked in:
36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2
Jan
next prev parent reply other threads:[~2015-05-16 12:58 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 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: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 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: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 6/7] compile: New 'compile print' Jan Kratochvil
2015-05-15 17:04 ` Pedro Alves
2015-05-16 12:58 ` Jan Kratochvil [this message]
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
2015-05-13 20:17 ` [PATCH v5 7/7] RFC only: compile: Use also inferior munmap 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=20150516125814.GE9862@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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