From: Hannes Domani <ssbssa@yahoo.de>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2][PR gdb/24789] Allow pointer arithmetic with integer references
Date: Wed, 1 Apr 2020 17:36:30 +0000 (UTC) [thread overview]
Message-ID: <576703007.1029840.1585762590985@mail.yahoo.com> (raw)
In-Reply-To: <537466658.992778.1585761470024@mail.yahoo.com>
Am Mittwoch, 1. April 2020, 19:17:58 MESZ hat Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> Folgendes geschrieben:
> Am Mittwoch, 1. April 2020, 18:36:47 MESZ hat Tom Tromey <tom@tromey.com> Folgendes geschrieben:
>
> > >>>>> "Hannes" == Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> writes:
> >
> > Hannes> 2020-04-01 Hannes Domani <ssbssa@yahoo.de>
> >
> > Hannes> PR gdb/24789
> > Hannes> * eval.c (is_integral_or_integral_reference): New function.
> > Hannes> (evaluate_subexp_standard): Allow integer references in
> > Hannes> pointer arithmetic.
> >
> > Thank you.
> >
> > Hannes> +/* Return true if type is integral or reference to integral */
> > Hannes> +
> > Hannes> +static bool
> > Hannes> +is_integral_or_integral_reference (struct type *type)
> > Hannes> +{
> > Hannes> + if (is_integral_type (type))
> > Hannes> + return true;
> > Hannes> +
> > Hannes> + type = check_typedef (type);
> > Hannes> + return type != nullptr
> > Hannes> + && TYPE_IS_REFERENCE (type)
> > Hannes> + && is_integral_type (TYPE_TARGET_TYPE (type));
> >
> > This needs parens around the multi-line expression, like:
> >
> >
> > return (type != nullptr
> > && TYPE_IS_REFERENCE (type)
> > && is_integral_type (TYPE_TARGET_TYPE (type)));
> >
> >
> > The patch is ok with this tweak.
>
> Pushed with this change, thanks.
That leads me to another question, who/when are PRs closed after pushing?
So in this case this one:
https://sourceware.org/bugzilla/show_bug.cgi?id=24789
And these are 2 other which I think should have been closed some time ago
after someone implemented it:
https://sourceware.org/bugzilla/show_bug.cgi?id=8684
https://sourceware.org/bugzilla/show_bug.cgi?id=14529
And these problems can no longer be reproduced since some versions:
https://sourceware.org/bugzilla/show_bug.cgi?id=17667
https://sourceware.org/bugzilla/show_bug.cgi?id=22541
https://sourceware.org/bugzilla/show_bug.cgi?id=17521
Hannes
next prev parent reply other threads:[~2020-04-01 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200331220655.4436-1-ssbssa.ref@yahoo.de>
2020-03-31 22:06 ` Hannes Domani
2020-04-01 16:36 ` Tom Tromey
2020-04-01 17:17 ` Hannes Domani
2020-04-01 17:36 ` Hannes Domani [this message]
2020-04-01 18:06 ` Tom Tromey
[not found] ` <87sghn2i0g.fsf@tromey.com>
2020-04-01 18:14 ` Hannes Domani
2020-04-01 18:55 ` 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=576703007.1029840.1585762590985@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--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