Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 1/6] Add initial type alignment support
Date: Tue, 24 Apr 2018 19:16:00 -0000	[thread overview]
Message-ID: <c46973d1-ab2f-2c50-4272-a6a3bb277b85@redhat.com> (raw)
In-Reply-To: <20180424152222.8053-2-tom@tromey.com>

Hi Tom,

On 04/24/2018 04:22 PM, Tom Tromey wrote:

> +/* * Number of bits allocated for alignment.  */
> +
> +#define TYPE_ALIGN_BITS 8
> +
>  /* * A ``struct type'' describes a particular instance of a type, with
>     some particular qualification.  */
>  
> @@ -831,6 +835,14 @@ struct type
>  
>    struct type *chain;
>  
> +  /* * The alignment for this type.  Zero means that the alignment was
> +     not specified in the debug info.  Note that this is stored in a
> +     funny way: as the log base 2 (plus 1) of the alignment; so a
> +     value of 1 means the alignment is 1, and a value of 9 means the
> +     alignment is 256.  */
> +
> +  unsigned align_log2 : TYPE_ALIGN_BITS;
> +
>    /* * Flags specific to this instance of the type, indicating where
>       on the ring we are.
>  
> @@ -841,7 +853,7 @@ struct type
>       instance flags are completely inherited from the target type.  No
>       qualifiers can be cleared by the typedef.  See also
>       check_typedef.  */
> -  int instance_flags;
> +  unsigned instance_flags : 9;
>  
>    /* * Length of storage for a value of this type.  The value is the
>       expression in host bytes of what sizeof(type) would return.  This
> @@ -1292,6 +1304,26 @@ extern void allocate_gnat_aux_type (struct type *);
>     so you only have to call check_typedef once.  Since allocate_value
>     calls check_typedef, TYPE_LENGTH (VALUE_TYPE (X)) is safe.  */
>  #define TYPE_LENGTH(thistype) (thistype)->length
> +
> +/* * Return the alignment of the type in bytes, or 0 if no alignment
> +   was specified.  */
> +#define TYPE_RAW_ALIGN(thistype) type_raw_align (thistype)
> +
> +/* * Return the alignment of the type in bytes, or 0 if no alignment
> +   was specified.  */
> +extern unsigned type_raw_align (struct type *);
> +
> +/* * Return the alignment of the type in bytes.  Return 0 if the
> +   alignment cannot be determined; but note that this makes an effort
> +   to compute the alignment even it it was not specified in the debug
> +   info.  */
> +extern unsigned type_align (struct type *);
> +
> +/* * Set the alignment of the type.  The alignment must be a power of
> +   2.  Returns false if the given value does not fit in the available
> +   space in struct type.  */
> +extern bool set_type_align (struct type *, ULONGEST);

Are these represented in host bytes, or target addressable memory units?
See comments around type::length and type_length_units.  The comments above
should be clarified in that direction.

> +/* Implement the type_align gdbarch function.  */
> +
> +static ULONGEST
> +i386_type_align (struct gdbarch *gdbarch, struct type *type)
> +{
> +  type = check_typedef (type);
> +
> +  if (gdbarch_ptr_bit (gdbarch) == 32 &&
> +      TYPE_CODE (type) == TYPE_CODE_INT && TYPE_LENGTH (type) > 4)
> +    return 4;

&& on the other line.

Otherwise looks good to me, but I'd like to hear Simon's opinion.

Thanks,
Pedro Alves


  reply	other threads:[~2018-04-24 19:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 15:22 [RFA 0/6] Teach gdb about type alignment Tom Tromey
2018-04-24 15:22 ` [RFA 3/6] Reindent type_object_getset in py-type.c Tom Tromey
2018-04-24 15:22 ` [RFA 4/6] Expose type alignment on gdb.Type Tom Tromey
2018-04-24 16:59   ` Eli Zaretskii
2018-04-24 15:22 ` [RFA 2/6] Handle alignof and _Alignof Tom Tromey
2018-04-24 17:04   ` Eli Zaretskii
2018-04-24 19:17   ` Pedro Alves
2018-04-24 20:23     ` Tom Tromey
2018-04-27 18:02       ` Pedro Alves
2018-04-27 20:53         ` Tom Tromey
2018-04-30 16:46         ` Tom Tromey
2018-04-26 20:45     ` Tom Tromey
2018-04-27 18:05       ` Pedro Alves
2018-04-26 20:54     ` Tom Tromey
2018-04-24 15:22 ` [RFA 6/6] Remove long_long_align_bit gdbarch attribute Tom Tromey
2018-04-24 15:24   ` Tom Tromey
2018-04-24 17:17   ` Anton Kolesov
2018-04-26 20:56     ` Tom Tromey
2018-04-24 15:22 ` [RFA 5/6] Remove rust_type_alignment Tom Tromey
2018-04-24 15:22 ` [RFA 1/6] Add initial type alignment support Tom Tromey
2018-04-24 19:16   ` Pedro Alves [this message]
2018-04-24 20:23     ` 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=c46973d1-ab2f-2c50-4272-a6a3bb277b85@redhat.com \
    --to=palves@redhat.com \
    --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