From: Joel Brobecker <brobecker@adacore.com>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: New ARI warning Fri Feb 27 01:54:21 UTC 2015
Date: Mon, 02 Mar 2015 15:02:00 -0000 [thread overview]
Message-ID: <20150302150155.GC4449@adacore.com> (raw)
In-Reply-To: <1663130.tPCgNL199S@ralph.baldwin.cx>
> Yes, I've tried to follow that in my other patches (some of which I haven't
> sent yet), but most of the code I work on follows the other style and old
> habits die hard. :)
:-)
> Not sure if these sorts of fixes need a ChangeLog entry as well, but does
> this address these?
Yes, all changes require a ChangeLog entry (I have this wild and
impossible dream that, one day, we will get rid of these ChangeLogs.
One day...)
> gdb/ChangeLog:
>
> * amd64fbsd-tdep.c (amd64fbsd_sigtramp_p): Style fixes.
> * i386fbsd-tdep.c (i386fbsd_sigtramp_p): Likewise.
> diff --git a/gdb/i386fbsd-tdep.c b/gdb/i386fbsd-tdep.c
> index d4516ee..ed41706 100644
> --- a/gdb/i386fbsd-tdep.c
> +++ b/gdb/i386fbsd-tdep.c
> @@ -105,24 +105,24 @@ static const gdb_byte i386fbsd_osigtramp_end[] =
> };
>
> /* The three different trampolines are all the same size. */
> -gdb_static_assert (sizeof i386fbsd_sigtramp_start ==
> - sizeof i386fbsd_freebsd4_sigtramp_start);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_start ==
> - sizeof i386fbsd_osigtramp_start);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_middle ==
> - sizeof i386fbsd_freebsd4_sigtramp_middle);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_middle ==
> - sizeof i386fbsd_osigtramp_middle);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_end ==
> - sizeof i386fbsd_freebsd4_sigtramp_end);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_end ==
> - sizeof i386fbsd_osigtramp_end);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_start
> + == sizeof i386fbsd_freebsd4_sigtramp_start);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_start
> + == sizeof i386fbsd_osigtramp_start);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_middle
> + == sizeof i386fbsd_freebsd4_sigtramp_middle);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_middle
> + == sizeof i386fbsd_osigtramp_middle);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_end
> + == sizeof i386fbsd_freebsd4_sigtramp_end);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_end
> + == sizeof i386fbsd_osigtramp_end);
>
> /* We assume that the middle is the largest chunk below. */
> -gdb_static_assert (sizeof i386fbsd_sigtramp_middle >
> - sizeof i386fbsd_sigtramp_start);
> -gdb_static_assert (sizeof i386fbsd_sigtramp_middle >
> - sizeof i386fbsd_sigtramp_end);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_middle
> + > sizeof i386fbsd_sigtramp_start);
> +gdb_static_assert (sizeof i386fbsd_sigtramp_middle
> + > sizeof i386fbsd_sigtramp_end);
You'll need to mention those in the ChangeLog as well.
Since there is no function as the context, I would probably say
something like this:
* i386fbsd-tdep.c: Fix style in various gdb_static_assert
expressions.
?
Otherwise, looks good to me.
Thanks!
--
Joel
next prev parent reply other threads:[~2015-03-02 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 1:54 GDB Administrator
2015-02-27 8:24 ` Joel Brobecker
2015-02-27 19:01 ` John Baldwin
2015-03-02 15:02 ` Joel Brobecker [this message]
2015-03-12 19:37 ` John Baldwin
2015-03-13 17:50 ` 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=20150302150155.GC4449@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=palves@redhat.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