Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org,
	John Darrington <john@darrington.wattle.id.au>
Subject: Re: [PATCH] GDB: S12Z: new function s12z_extract_return_value
Date: Tue, 20 Nov 2018 17:01:00 -0000	[thread overview]
Message-ID: <20181120170124.hssaj76bdwcpfu6b@jocasta.intra> (raw)
In-Reply-To: <20181120094031.731d359b@pinnacle.lan>

On Tue, Nov 20, 2018 at 09:40:31AM -0700, Kevin Buettner wrote:
     On Tue, 20 Nov 2018 08:56:26 +0100
     John Darrington <john@darrington.wattle.id.au> wrote:
     
     > Make gdb aware of the return values of functions which
     > return in registers.
     > 
     > gdb/ChangeLog:
     > * s12z-tdep.c (s12z_extract_return_value): New function.
     >   (inv_reg_perm) New array.
     >   (s12z_return_value): Populate readbuf if non-null.
     
     Okay.  (But make sure that the leading spaces get changed to a single
     tab when you place your ChangeLog entry in the ChangeLog file.)
     

Thanks.  I will do that.

(If I remember rightly however, the link you posted earlier explicitly
stated that the leading whitespace should be 8 spaces.  But as all other
entries have used tabs it seems best to be consistent.)


J'


  reply	other threads:[~2018-11-20 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  9:18 [PATCH 1/2] GDB: S12Z: Add assertion John Darrington
2018-11-12  9:18 ` [PATCH 2/2] GDB: S12Z: new function s12z_extract_return_value John Darrington
2018-11-18  6:35   ` Kevin Buettner
2018-11-18  9:13     ` John Darrington
2018-11-18 18:28       ` Kevin Buettner
2018-11-20  7:56     ` [PATCH] " John Darrington
2018-11-20 16:40       ` Kevin Buettner
2018-11-20 17:01         ` John Darrington [this message]
2018-11-17 21:59 ` [PATCH 1/2] GDB: S12Z: Add assertion Kevin Buettner
2018-11-18  9:23   ` John Darrington
2018-11-18 18:42     ` Kevin Buettner
2018-11-19 16:09       ` Joel Brobecker
2018-11-19 16:47   ` [PATCH] " John Darrington
2018-11-20  5:16     ` Kevin Buettner

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=20181120170124.hssaj76bdwcpfu6b@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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