Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 4/5] gdb: Introduce new language field la_is_string_type_p
Date: Fri, 19 Apr 2019 14:45:00 -0000	[thread overview]
Message-ID: <878sw6dpg0.fsf@tromey.com> (raw)
In-Reply-To: <dc4d48cfd02d2d37d6bbaf7374118dcbca56ec2e.1555455013.git.andrew.burgess@embecosm.com>	(Andrew Burgess's message of "Wed, 17 Apr 2019 00:06:09 +0100")

>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:

Andrew> Some languages already have a "is this a string" predicate that I was
Andrew> able to reuse, while for other languages I've had to add a new
Andrew> predicate.  In this case I took inspiration from the value printing
Andrew> code for that language - what different conditions would result in
Andrew> printing something as a string.

This looks essentially fine, but I had some questions.

Andrew> +bool
Andrew> +c_is_string_type_p (struct type *type)
Andrew> +{
Andrew> +  type = check_typedef (type);
Andrew> +  while (TYPE_CODE (type) == TYPE_CODE_REF)
Andrew> +    {
Andrew> +      type = TYPE_TARGET_TYPE (type);
Andrew> +      type = check_typedef (type);
Andrew> +    }
Andrew> +
Andrew> +  switch (TYPE_CODE (type))
Andrew> +    {
Andrew> +    case TYPE_CODE_ARRAY:
Andrew> +      {
Andrew> +	/* See if target type looks like a string.  */
Andrew> +	struct type *array_target_type = TYPE_TARGET_TYPE (type);
Andrew> +	return (TYPE_LENGTH (type) > 0
Andrew> +		&& TYPE_LENGTH (array_target_type) > 0
Andrew> +		&& c_textual_element_type (array_target_type, 0));
Andrew> +      }
Andrew> +    case TYPE_CODE_STRING:
Andrew> +      return true;

It seems to me that a "char *" should be considered a string in C;
and probably a "wchar_t *" as well.  Maybe see c-lang.c:classify_type.

Andrew> +/* Return true if TYPE is a string type.  */
Andrew> +static bool
Andrew> +rust_is_string_type_p (struct type *type)
Andrew> +{
Andrew> +  LONGEST low_bound, high_bound;
Andrew> +
Andrew> +  type = check_typedef (type);
Andrew> +  return ((TYPE_CODE (type) == TYPE_CODE_STRING)
Andrew> +	  || (TYPE_CODE (type) == TYPE_CODE_PTR
Andrew> +	      && (TYPE_CODE (TYPE_TARGET_TYPE (type)) == TYPE_CODE_ARRAY
Andrew> +		  && rust_u8_type_p (TYPE_TARGET_TYPE (TYPE_TARGET_TYPE (type)))
Andrew> +		  && get_array_bounds (TYPE_TARGET_TYPE (type), &low_bound,
Andrew> +				       &high_bound)))
Andrew> +	  || ((TYPE_CODE (type) == TYPE_CODE_UNION
Andrew> +	       || (TYPE_CODE (type) == TYPE_CODE_STRUCT
Andrew> +		   && !rust_enum_p (type)))
Andrew> +	      && rust_slice_type_p (type)
Andrew> +	      && strcmp (TYPE_NAME (type), "&str") == 0));

I didn't understand the reason for TYPE_CODE_UNION here.

Also, I think an array or slice of 'char' should probably be considered
a string in Rust.  See rust_chartype_p.

thanks,
Tom


  parent reply	other threads:[~2019-04-19 14:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 23:06 [PATCHv2 0/5] Add new 'print max-depth' feature Andrew Burgess
2019-03-27 21:53 ` [PATCH 0/2] " Andrew Burgess
2019-03-27 21:53   ` [PATCH 2/2] gdb: Introduce " Andrew Burgess
2019-03-28 16:08     ` Eli Zaretskii
2019-03-27 21:53   ` [PATCH 1/2] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-03-28 12:43     ` Pedro Alves
2019-03-28 12:47   ` [PATCH 0/2] Add new 'print max-depth' feature Pedro Alves
2019-03-28 22:48     ` Andrew Burgess
2019-03-28 23:47       ` Marco Barisione
2019-04-16 23:06   ` [PATCHv2 1/5] gdb/ada: Update some predicate functions to return bool Andrew Burgess
2019-04-18  0:03     ` Joel Brobecker
2019-04-16 23:06   ` [PATCHv2 4/5] gdb: Introduce new language field la_is_string_type_p Andrew Burgess
2019-04-18 17:08     ` Pedro Alves
2019-04-19 21:00       ` Andrew Burgess
2019-04-19 14:45     ` Tom Tromey [this message]
2019-04-19 22:22       ` Andrew Burgess
2019-04-24 19:32         ` Tom Tromey
2019-04-19 22:45       ` Andrew Burgess
2019-04-24 19:33         ` Tom Tromey
2019-04-16 23:06   ` [PATCHv2 3/5] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-04-19 14:37     ` Tom Tromey
2019-04-16 23:06   ` [PATCHv2 2/5] gdb/testsuite: Don't add gcc flags when compiling rust tests Andrew Burgess
2019-04-19 14:31     ` Tom Tromey
2019-04-16 23:06   ` [PATCHv2 5/5] gdb: Introduce 'print max-depth' feature Andrew Burgess
2019-04-17  7:42     ` Philippe Waroquiers
2019-04-17 14:35     ` Eli Zaretskii
2019-04-18  1:07       ` Andrew Burgess
2019-04-18  2:38         ` Eli Zaretskii
2019-04-18 21:52           ` Andrew Burgess
2019-04-19  6:50             ` Eli Zaretskii
2019-04-18 17:08     ` Pedro Alves
2019-04-29 21:14 ` [PATCHv2 0/5] Add new " Andrew Burgess

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=878sw6dpg0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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