public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Victor Kamensky <victor.kamensky@linaro.org>
To: gdb-patches@sourceware.org,	Yao Qi <yao@codesourcery.com>
Cc: Andrew Pinski <pinskia@gmail.com>,	victor.kamensky@linaro.org
Subject: [RFC PATCH 0/2] couple big endian fixes in testsuites
Date: Mon, 27 Oct 2014 03:16:00 -0000	[thread overview]
Message-ID: <1414379778-5478-1-git-send-email-victor.kamensky@linaro.org> (raw)

Hi Folks,

While I was working on arm V7 and V8 big endian issues. I noticed
couple gdb test cases that had endianity issues in test themselves.
There were failures in implptrpiece.exp and py-value-cc.exp. I
verified that ppc 64bit big endian failed those test as well.

My attempt to address endian issues in those test follows this
cover letter.

Thanks,
Victor

Victor Kamensky (2):
  fix implptrpiece.exp test for big endian target
  fix py-value-cc.exp test for big endian target

 gdb/testsuite/gdb.dwarf2/implptrpiece.exp | 13 ++++++++++++-
 gdb/testsuite/gdb.python/py-value-cc.cc   |  2 +-
 gdb/testsuite/gdb.python/py-value-cc.exp  |  4 ++--
 3 files changed, 15 insertions(+), 4 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2014-10-27  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  3:16 Victor Kamensky [this message]
2014-10-27  3:16 ` [RFC PATCH 2/2] fix py-value-cc.exp test for big endian target Victor Kamensky
2014-10-29  6:40   ` Yao Qi
2014-10-29  9:13     ` Pedro Alves
2014-10-27  3:16 ` [RFC PATCH 1/2] fix implptrpiece.exp " Victor Kamensky
2014-10-29  8:15   ` 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=1414379778-5478-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).