Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, gdb@sourceware.org,
		Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [patch] Re: Regression: field type preservation: 7.0 ->  7.0.1+HEAD
Date: Sun, 03 Jan 2010 04:58:00 -0000	[thread overview]
Message-ID: <20100103045717.GZ2788@adacore.com> (raw)
In-Reply-To: <20100102203022.GA8372@host0.dyn.jankratochvil.net>

> gdb/
> 2010-01-02  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* value.c (value_primitive_field): Remove one check_typedef call.
> 	Move bitpos and container_bitsize initialization after
> 	allocate_value_lazy.  New comment before accessing TYPE_LENGTH.

Interesting. This patch allowed me to figure out why the initial patch
sent by Vladimir was in fact working when it looks like it could not
possibly work :).

Personally, I'm not a big fan of the approach you took in this case.
You rely on a side-effect of the various allocate_* routines, but
this is only because these routines call check_typedef. In particular,
there is something interesting in allocate_value_lazy. A variable is
declared...

        struct type *atype = check_typedef (type);

... but then never used. There is no available info as to why this is,
as this is here since day 1 of the public CVS repo, but it's now clear
to me that this helps fixing that length - a type length that does not
appear to be used at all in the rest of the routine!

In my opinion, I agree with Daniel's comment that it is unusual to
call check_typedef without storing the function result.  But this
seems to be less awkward than relying on an undocumented side-effect
of a function that uses an undocumented side-effect of a check_typedef,
especially since the function in question does not really need that
side-effect to be applied at the time the function is called!

So, my proposal, if the other maintainers agree, is to document
the side-effect of check_typedef (sets the typedef TYPE_LENGTH)
as this appears to be a fully-intended behavior, and then do:

> -  type = check_typedef (type);

> +  /* Call check_typedef on our type to make sure that, if TYPE
> +     is a TYPE_CODE_TYPEDEF, its length is set to the length
> +     of the target type instead of zero.  However, we do not
> +     replace the typedef type by the target type, because we want
> +     to keep the typedef in order to be able to print the type
> +     description correctly.  */
> +  check_typedef (type);

> gdb/testsuite/
> 2010-01-02  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdb.mi/var-cmd.c (do_bitfield_tests): Change "V.sharable" type to
> 	"uint_for_mi_testing".

This part is OK.

-- 
Joel


  reply	other threads:[~2010-01-03  4:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100101184505.GA18391@host0.dyn.jankratochvil.net>
     [not found] ` <201001021308.19130.vladimir@codesourcery.com>
2010-01-02 20:30   ` Jan Kratochvil
2010-01-03  4:58     ` Joel Brobecker [this message]
2010-01-03  5:48       ` Jan Kratochvil
2010-01-03  6:03         ` Joel Brobecker
2010-01-03 17:06           ` Daniel Jacobowitz
2010-01-03 19:26             ` Jan Kratochvil
2010-01-03 21:52               ` Daniel Jacobowitz
2010-01-03 22:14                 ` Jan Kratochvil
2010-01-05 17:49       ` 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=20100103045717.GZ2788@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=vladimir@codesourcery.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