Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Jim Wilson <jimw@sifive.com>, John Baldwin <jhb@freebsd.org>,
	Palmer Dabbelt <palmer@sifive.com>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH 0/2] More type_align fixes
Date: Thu, 11 Apr 2019 22:42:00 -0000	[thread overview]
Message-ID: <20190411224213.GD2737@embecosm.com> (raw)
In-Reply-To: <cover.1554672869.git.andrew.burgess@embecosm.com>

* Andrew Burgess <andrew.burgess@embecosm.com> [2019-04-07 22:37:53 +0100]:

> This short series finally removes the riscv_type_alignment function
> and replaces it with use of the common type_align function.
> 
> I found one more fix that was needed in order to allow this change
> (patch #1), then the switch over is simple (patch #2).
> 
> --
> 
> Andrew Burgess (2):
>   gdb: Fix alignment computation for structs with only static fields
>   gdb/riscv: Remove riscv_type_alignment function

I've pushed both of these patches now.

Thanks,
Andrew



> 
>  gdb/ChangeLog                    | 12 ++++++++
>  gdb/gdbtypes.c                   | 12 ++++----
>  gdb/riscv-tdep.c                 | 60 ++++++++--------------------------------
>  gdb/testsuite/ChangeLog          |  5 ++++
>  gdb/testsuite/gdb.base/align.exp | 24 ++++++++++++----
>  5 files changed, 53 insertions(+), 60 deletions(-)
> 
> -- 
> 2.14.5
> 


      parent reply	other threads:[~2019-04-11 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 21:38 Andrew Burgess
2019-04-07 21:38 ` [PATCH 2/2] gdb/riscv: Remove riscv_type_alignment function Andrew Burgess
2019-04-07 21:38 ` [PATCH 1/2] gdb: Fix alignment computation for structs with only static fields Andrew Burgess
2019-04-07 22:36   ` Tom Tromey
2019-04-11 22:42 ` Andrew Burgess [this message]

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=20190411224213.GD2737@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=jimw@sifive.com \
    --cc=palmer@sifive.com \
    --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