From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Marius Muench <marius.muench@eurecom.fr>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] ARM: Do not use FP reg when on AAPCS
Date: Thu, 25 Oct 2018 20:34:00 -0000 [thread overview]
Message-ID: <20181025133418.68b513e1@pinnacle.lan> (raw)
In-Reply-To: <15364ecd-125d-7196-8e83-e6db60127005@eurecom.fr>
On Wed, 24 Oct 2018 21:37:07 +0200
Marius Muench <marius.muench@eurecom.fr> wrote:
> Fair enough, updated version below.
>
> gdb/ChangeLog:
> 2018-10-24 Marius Muench <marius.muench@eurecom.fr>
>
> * arm-tdep.c (arm_scan_prologue): Don't dereference FP reg
> when on AAPCS.
Looks good to me.
You can commit / push this now...
Kevin
next prev parent reply other threads:[~2018-10-25 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 13:03 Marius Muench
2018-10-23 17:16 ` Kevin Buettner
2018-10-24 11:40 ` Marius Muench
2018-10-24 16:47 ` Kevin Buettner
2018-10-24 17:23 ` Pedro Alves
2018-10-24 19:37 ` Marius Muench
2018-10-25 20:34 ` Kevin Buettner [this message]
2018-10-26 12:13 ` Marius Muench
2018-11-06 17:53 ` 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=20181025133418.68b513e1@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marius.muench@eurecom.fr \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).