From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA v2 2/6] Handle alignof and _Alignof
Date: Fri, 27 Apr 2018 18:47:00 -0000 [thread overview]
Message-ID: <2acfa770-0ec2-b675-a139-f350aa059da0@redhat.com> (raw)
In-Reply-To: <20180427140139.7957-3-tom@tromey.com>
On 04/27/2018 03:01 PM, Tom Tromey wrote:
> This adds alignof and _Alignof to the C/C++ expression parser, and
> adds new tests to test the features. The tests are written to try to
> ensure that gdb's knowledge of alignment rules stays in sync with the
> compiler's.
This looks good to me. A few comments on additional tests below,
but there's no need for another round of review for those.
> +++ b/gdb/testsuite/gdb.cp/align.exp
> @@ -0,0 +1,145 @@
...
> +
> +# Prologue.
> +puts $outfile {
> + template<typename T, typename U>
> + struct align_pair
> + {
> + T one;
> + U two;
> + };
> +
> + template<typename T, typename U>
> + struct align_union
> + {
> + T one;
> + U two;
> + };
> +
> + enum bigenum { VALUE = 0xffffffffull };
> +
> + struct empty { };
> +
> + struct vstruct { virtual ~vstruct() {} char c; };
> +
> + struct bfstruct { unsigned b : 3; };
> +
> + struct arrstruct { short fld[7]; };
Sorry to be a drag, but I think it'd be good to add a few
more tests here:
- alignof(typedef)
(to make sure we're not missing a check_typedef
call somewhere. e.g., add "typedef arrstruct arrstruct_t",
then add arrstruct_t to the list of tested types.
- alignof(a class with a base class).
E.g.,:
struct A { int i;};
struct B : A { char c; };
and then check alignof(B).
multiple and virtual inheritance might be worth
testing too, not sure whether the code paths are
(and will always be) the same.
- alignof(array-type)
This is what I actually meant by arrays in v1. E.g.:
alignof (int[3])
It might be we don't parse that. Not sure. If it's hard,
it's ok to punt, but then it'd be good to still add the test
and kfail it.
> +proc maybe_xfail {type} {
> + # See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69560
> + # The g++ implementation of alignof is changing to match C11.
> + if {[is_x86_like_target]
> + && ($type == "double" || $type == "long long"
> + || $type == "unsigned long long")} {
> + setup_xfail *-*-*
It seems like we can check for gcc version with test_compiler_info.
Maybe go ahead and limit the xfail to:
[test_compiler_info {gcc-[0-8]-*}]
?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-27 18:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 14:01 [RFA v2 0/6] Type alignment Tom Tromey
2018-04-27 14:01 ` [RFA v2 4/6] Expose type alignment on gdb.Type Tom Tromey
2018-04-27 14:18 ` Eli Zaretskii
2018-04-27 18:47 ` Pedro Alves
2018-04-27 20:41 ` Tom Tromey
2018-04-27 14:01 ` [RFA v2 5/6] Remove rust_type_alignment Tom Tromey
2018-04-27 14:01 ` [RFA v2 6/6] Remove long_long_align_bit gdbarch attribute Tom Tromey
2018-04-27 18:47 ` Pedro Alves
2018-04-27 14:01 ` [RFA v2 2/6] Handle alignof and _Alignof Tom Tromey
2018-04-27 14:19 ` Eli Zaretskii
2018-04-27 18:47 ` Pedro Alves [this message]
2018-04-27 20:55 ` Tom Tromey
2018-04-27 20:59 ` Tom Tromey
2018-04-30 16:50 ` Tom Tromey
2018-04-30 17:17 ` Pedro Alves
2018-04-27 14:01 ` [RFA v2 3/6] Reindent type_object_getset in py-type.c Tom Tromey
2018-04-27 18:47 ` Pedro Alves
2018-04-27 20:39 ` Tom Tromey
2018-04-27 14:01 ` [RFA v2 1/6] Add initial type alignment support Tom Tromey
2018-04-27 18:46 ` Pedro Alves
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=2acfa770-0ec2-b675-a139-f350aa059da0@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