Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/6] Remove some manual memory management from compile interface
Date: Sat, 19 Sep 2020 19:52:33 -0400	[thread overview]
Message-ID: <266736d8-415c-b18e-507f-c8e5fbe84231@simark.ca> (raw)
In-Reply-To: <87pn6h5o1s.fsf@tromey.com>


On 2020-09-19 7:45 p.m., Tom Tromey wrote:
> Simon> You could now remove this `if (num_baseclasses > 0)`, there's no
> Simon> reason for it anymore I think.
>
> I looked at this more deeply, and based on the compiler library, I think
> the rule is that a 0-length array should be passed as nullptr here:
>
>   status
>   marshall (connection *conn, const gcc_vbase_array *a)
>   {
>     size_t len;
>
>     if (a)
>       len = a->n_elements;
>     else
>       len = (size_t)-1;
>
>     if (!marshall_array_start (conn, 'v', len))
>       return FAIL;
>
>     if (!a)
>       return OK;
>    [...]
>
>
> So, I changed this code to use your suggestion and then also modified
> the final call:
>
>       result = instance->plugin ().start_class_type
> 	(name.get (), resuld, num_baseclasses > 0 ? &bases : nullptr,
> 	 filename, line);
>
> This didn't result in any test result changes, but I didn't look to see
> if this case is not tested or something like that.

Oh, I didn't realize that the change I proposed would change how we call
the function.  What you ended up doing makes sense, if that's what's the
compiler library expects.

Simon


  reply	other threads:[~2020-09-19 23:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 13:52 [PATCH 0/6] Avoid manual memory management in gdb/compile/ Tom Tromey
2020-08-09 13:52 ` [PATCH 1/6] Remove some manual memory management from compile interface Tom Tromey
2020-08-09 22:34   ` Simon Marchi
2020-09-19 23:45     ` Tom Tromey
2020-09-19 23:52       ` Simon Marchi [this message]
2020-09-23 12:56         ` Tom Tromey
2020-08-09 13:52 ` [PATCH 2/6] Use new/delete for do_module_cleanup Tom Tromey
2020-08-09 22:45   ` [PP?] " Simon Marchi
2020-09-23 13:36     ` Tom Tromey
2020-08-09 13:52 ` [PATCH 3/6] Introduce and use compile_module_up Tom Tromey
2020-08-09 13:52 ` [PATCH 4/6] Transfer module ownership to do_module_cleanup Tom Tromey
2020-08-10  0:48   ` [PP?] " Simon Marchi
2020-09-23 14:55     ` Tom Tromey
2020-08-09 13:52 ` [PATCH 5/6] Simplify compile_module cleanup Tom Tromey
2020-08-09 13:52 ` [PATCH 6/6] Avoid manual memory management of argv arrays in gdb/compile Tom Tromey

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=266736d8-415c-b18e-507f-c8e5fbe84231@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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