Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Hannes Domani <ssbssa@yahoo.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][PR gdb/18706] Calculate size of array of stubbed type
Date: Tue, 28 Apr 2020 11:10:27 -0400	[thread overview]
Message-ID: <82e2e5d4-f5e3-7a89-5bcb-bfe305c601e4@simark.ca> (raw)
In-Reply-To: <20200427114154.2275-1-ssbssa@yahoo.de>

On 2020-04-27 7:41 a.m., Hannes Domani via Gdb-patches wrote:
> Sizes of stubbed types are calculated on demand in check_typedef, so the same
> must also be done for arrays of stubbed types.

For the uninitiated, can you please explain what's happening here, which types
are involved, which ones are stubs, and what that means.  That would help me
understand what happens here and be confident that the patch is correct.

> 
> gdb/ChangeLog:
> 
> 2020-04-27  Hannes Domani  <ssbssa@yahoo.de>
> 
> 	PR gdb/18706
> 	* gdbtypes.c (check_typedef): Calculate size of array of stubbed type.
> 
> gdb/testsuite/ChangeLog:
> 
> 2020-04-27  Hannes Domani  <ssbssa@yahoo.de>
> 
> 	PR gdb/18706
> 	* gdb.cp/stub-array-size.cc: New test.
> 	* gdb.cp/stub-array-size.exp: New file.
> 	* gdb.cp/stub-array-size.h: New test.
> 	* gdb.cp/stub-array-size2.cc: New test.
> ---
>  gdb/gdbtypes.c                           | 16 ++++++++++++++
>  gdb/testsuite/gdb.cp/stub-array-size.cc  | 25 ++++++++++++++++++++++
>  gdb/testsuite/gdb.cp/stub-array-size.exp | 27 ++++++++++++++++++++++++
>  gdb/testsuite/gdb.cp/stub-array-size.h   | 21 ++++++++++++++++++
>  gdb/testsuite/gdb.cp/stub-array-size2.cc | 22 +++++++++++++++++++
>  5 files changed, 111 insertions(+)
>  create mode 100644 gdb/testsuite/gdb.cp/stub-array-size.cc
>  create mode 100644 gdb/testsuite/gdb.cp/stub-array-size.exp
>  create mode 100644 gdb/testsuite/gdb.cp/stub-array-size.h
>  create mode 100644 gdb/testsuite/gdb.cp/stub-array-size2.cc
> 
> diff --git a/gdb/gdbtypes.c b/gdb/gdbtypes.c
> index 157b3c5e61..5e9de2ccb1 100644
> --- a/gdb/gdbtypes.c
> +++ b/gdb/gdbtypes.c
> @@ -2637,6 +2637,22 @@ check_typedef (struct type *type)
>  	  TYPE_LENGTH (type) = TYPE_LENGTH (target_type);
>  	  TYPE_TARGET_STUB (type) = 0;
>  	}
> +      else if (TYPE_CODE (type) == TYPE_CODE_ARRAY
> +	       && TYPE_NFIELDS (type) == 1)

Why is the `TYPE_NFIELDS (type) == 1` check necessary here?

> +	{
> +	  struct type *range_type = check_typedef (TYPE_INDEX_TYPE (type));
> +	  if (TYPE_CODE (range_type) == TYPE_CODE_RANGE
> +	      && has_static_range (TYPE_RANGE_DATA (range_type)))

Is it possible to have an array type where the index type is not TYPE_CODE_RANGE?

If it is not, then we should assert `TYPE_CODE (range_type) == TYPE_CODE_RANGE`.  If it
can be of another type, what are the other possibilities?

> diff --git a/gdb/testsuite/gdb.cp/stub-array-size.exp b/gdb/testsuite/gdb.cp/stub-array-size.exp
> new file mode 100644
> index 0000000000..cb486cd459
> --- /dev/null
> +++ b/gdb/testsuite/gdb.cp/stub-array-size.exp
> @@ -0,0 +1,27 @@
> +# Copyright 2020 Free Software Foundation, Inc.
> +#
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
> +
> +# This file is part of the gdb testsuite.

Please add a short introductory comment that explains what this intends to test.

Simon


  reply	other threads:[~2020-04-28 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200427114154.2275-1-ssbssa.ref@yahoo.de>
2020-04-27 11:41 ` Hannes Domani
2020-04-28 15:10   ` Simon Marchi [this message]
2020-04-29 12:47     ` Hannes Domani
2020-04-29 16:39       ` Simon Marchi
2020-04-29 16:58         ` Hannes Domani
2020-04-29 18:26           ` Simon Marchi

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=82e2e5d4-f5e3-7a89-5bcb-bfe305c601e4@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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