From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] default_type_align: Use type_length_units
Date: Thu, 14 Jun 2018 16:59:00 -0000 [thread overview]
Message-ID: <877en1e23t.fsf@tromey.com> (raw)
In-Reply-To: <1528928623-27479-1-git-send-email-simon.marchi@ericsson.com> (Simon Marchi's message of "Wed, 13 Jun 2018 18:23:43 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> The type alignment value is returned in 8-bit-bytes instead of target
Simon> memory addressable units. For example, on a target with 16-bit-bytes
Simon> where sizeof(int) == 1 (one addressable unit), alignof(int) currently
Simon> returns 2. After, this patch, it returns 1.
Simon> * arch-utils.c (default_type_align): Use type_length_units.
This certainly is correct according to the comment in gdbtypes.h:
/* * Return the alignment of the type in target addressable memory
units.
However, I was curious to know what DWARF specifies, to see whether
dwarf2read was doing this as well. But DWARF seems pretty silent on
this topic:
A debugging information entry may have a DW_AT_alignment attribute
whose value of class constant is a positive, non-zero, integer
describing the alignment of the entity.
So maybe this is depending on what your compiler does? I think I did
not really consider this issue too deeply when writing the alignment
support :(
Another possible issue is that gdbtypes.c:type_align uses TYPE_LENGTH in
one spot but I suppose it ought to use type_length_units if this patch
goes in.
Tom
next prev parent reply other threads:[~2018-06-14 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 22:24 Simon Marchi
2018-06-14 16:59 ` Tom Tromey [this message]
2018-06-14 18:26 ` Simon Marchi
2018-06-14 19:50 ` Tom Tromey
2018-06-14 22:28 ` Simon Marchi
2018-06-15 16:43 ` 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=877en1e23t.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).