From: Victor Kamensky <victor.kamensky@linaro.org>
To: Yao Qi <yao@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/5] arm: set of big endian related fixes for armeb (v7)
Date: Wed, 22 Oct 2014 05:39:00 -0000 [thread overview]
Message-ID: <CAA3XUr2gzavm5tM_i5QknSdfFxsjSxaQXG2V5FV6MqpH0gKW2g@mail.gmail.com> (raw)
In-Reply-To: <8761fdkh8q.fsf@codesourcery.com>
Hi Yao,
Thank you for your help and attention! Please see response inline.
On 21 October 2014 00:35, Yao Qi <yao@codesourcery.com> wrote:
> Victor Kamensky <victor.kamensky@linaro.org> writes:
>
>> Note there are several failures remain that are not addressed by this
>> series. I.e valgrind related test cases all failed, because valgrind does
>> not support armeb target. There are other failures in a bit obscure
>> places like gdb.dwarf2/implptrpiece.exp, gdb.python/py-value-cc.exp,
>> but over all number of passes/failures significantly improved in armeb
>> case.
>
> Out of my curiosity, do you plan to address the rest of fails you
> mentioned above?
Not sure yet. Maybe on the second pass. Currently I am working
on aarch64 BE vs LE gdb testsuite result differences. There are few
issues in BE aarch64 case that affect gdb functionality visible to gdb
user.
I believe that remaining differences in ARM V7 BE test results most
likely are issues in test cases. And I am not sure whether it is more
general BE vs LE issues. I would probably give it a spin on BE ppc
and see how tests in question behave there.
Problems related to valgrind will not be addressed any time soon. It
seems it is huge thing to make valgrind to work in ARM V7 BE case.
Thanks,
Victor
> --
> Yao (齐尧)
next prev parent reply other threads:[~2014-10-22 5:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 0:57 Victor Kamensky
2014-10-21 0:57 ` [PATCH 5/5] ARM: asm-source.exp link options in case of armv7b target Victor Kamensky
2014-10-24 6:10 ` Yao Qi
2014-10-24 6:35 ` Victor Kamensky
2014-10-24 6:38 ` Andrew Pinski
2014-10-24 8:57 ` Yao Qi
2014-10-24 17:11 ` Victor Kamensky
2014-10-21 0:57 ` [PATCH 4/5] ARM: read_pieced_value do big endian processing only in case of valid gdb_regnum Victor Kamensky
2014-10-22 9:31 ` Yao Qi
2014-10-22 15:27 ` Victor Kamensky
2014-10-23 3:22 ` Yao Qi
2014-10-23 5:43 ` Victor Kamensky
2014-10-23 6:24 ` Yao Qi
2014-10-21 0:57 ` [PATCH 2/5] ARM: extract_arm_insn function need to read instrs correctly in be8 case Victor Kamensky
2014-10-21 7:58 ` Yao Qi
2014-10-21 8:04 ` Yao Qi
2014-10-21 14:45 ` Victor Kamensky
2014-10-24 12:20 ` gdb/CONTRIBUTE Pedro Alves
2014-10-24 17:36 ` gdb/CONTRIBUTE Victor Kamensky
2014-10-21 0:57 ` [PATCH 3/5] ARM: arm_breakpoint should be little endian form in case for arm BE8 Victor Kamensky
2014-10-21 8:13 ` Yao Qi
2014-10-21 0:57 ` [PATCH 1/5] ARM: plt_size functions need to read instructions in right byte order Victor Kamensky
2014-10-21 1:12 ` [PATCH 0/5] arm: set of big endian related fixes for armeb (v7) Andrew Pinski
2014-10-21 5:22 ` Victor Kamensky
2014-10-21 7:39 ` Yao Qi
2014-10-22 5:39 ` Victor Kamensky [this message]
2014-10-22 9:36 ` 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=CAA3XUr2gzavm5tM_i5QknSdfFxsjSxaQXG2V5FV6MqpH0gKW2g@mail.gmail.com \
--to=victor.kamensky@linaro.org \
--cc=gdb-patches@sourceware.org \
--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