From: Victor Kamensky <victor.kamensky@linaro.org>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>, Andrew Pinski <pinskia@gmail.com>,
victor.kamensky@linaro.org
Subject: [PATCH 0/2] aarch64 couple big endian fixes
Date: Mon, 27 Oct 2014 03:14:00 -0000 [thread overview]
Message-ID: <1414379668-5351-1-git-send-email-victor.kamensky@linaro.org> (raw)
Hi Folks,
Here are couple fixes for aarch64 (ARM 64bit) to address gdb testsuite
failures in aarch64 big endian case. Basically there were issue with
handling floating point registers and issue of going over signal frame.
After these fixes and couple other big endian related fixes
in test cases themseves (will be posted separately), aarch64 big endian
passes gdb testsuite in par with little endian results.
Also I run x86_64 and ppc64 gdb and aarch64 little endian testsuites
before/after to check that there is any regression.
Thanks,
Victor
Victor Kamensky (2):
aarch64: handle big endian float registers correctly
aarch64: tramp_frame_start function need to read instrs correctly in
be8 case
gdb/aarch64-tdep.c | 57 ++++++++++++++++++++++++++++++++++--------------------
gdb/tramp-frame.c | 2 +-
2 files changed, 37 insertions(+), 22 deletions(-)
--
1.8.1.4
next reply other threads:[~2014-10-27 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 3:14 Victor Kamensky [this message]
2014-10-27 3:14 ` [PATCH 1/2] aarch64: handle big endian float registers correctly Victor Kamensky
2014-10-27 3:14 ` [PATCH 2/2] aarch64: tramp_frame_start function need to read instrs correctly in be8 case Victor Kamensky
2014-10-29 6:07 ` Yao Qi
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=1414379668-5351-1-git-send-email-victor.kamensky@linaro.org \
--to=victor.kamensky@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.com \
--cc=yao@codesourcery.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).