public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Victor Kamensky <victor.kamensky@linaro.org>
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: Tue, 21 Oct 2014 01:12:00 -0000	[thread overview]
Message-ID: <CA+=Sn1mcMzqv14ZMCQN0FcqXXhJ8GHhgiT4cme1JPie-jVxs3g@mail.gmail.com> (raw)
In-Reply-To: <1413853021-4393-1-git-send-email-victor.kamensky@linaro.org>

On Mon, Oct 20, 2014 at 5:56 PM, Victor Kamensky
<victor.kamensky@linaro.org> wrote:
> Hi Folks,
>
> Please find five patches following this cover letter that address several
> big endian related issues for ARM V7 target. Problems were discovered by
> running gdb/testsuite on armeb (big endian) target rootfs/kernel and
> comparing results from the same source against arm (little endian).
>
> 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.
>
> Please note it is my first attempt to contribute into gdb. If I missed
> something please guide me how I can correct that.

Yes bfd patches need to be also sent to binutils@.

Thanks,
Andrew Pinski


>
> Thanks,
> Victor
>
> Victor Kamensky (5):
>   ARM: plt_size functions need to read instructions in right byte order
>   ARM: extract_arm_insn function need to read instrs correctly in be8
>     case
>   ARM: arm_breakpoint should be little endian form in case for arm BE8
>   ARM: read_pieced_value do big endian processing only in case of valid
>     gdb_regnum
>   ARM: asm-source.exp link options in case of armv7b target
>
>  bfd/ChangeLog                        |  9 +++++++
>  bfd/elf32-arm.c                      | 48 +++++++++++++++++++++++++++++++++---
>  gdb/ChangeLog                        | 16 ++++++++++++
>  gdb/arm-linux-tdep.c                 |  2 +-
>  gdb/arm-tdep.c                       |  2 +-
>  gdb/dwarf2loc.c                      | 30 +++++++++++-----------
>  gdb/testsuite/ChangeLog              |  4 +++
>  gdb/testsuite/gdb.asm/asm-source.exp |  4 +++
>  8 files changed, 94 insertions(+), 21 deletions(-)
>
> --
> 1.8.1.4
>

  parent reply	other threads:[~2014-10-21  1:12 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 1/5] ARM: plt_size functions need to read instructions in right byte order 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 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 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  1:12 ` Andrew Pinski [this message]
2014-10-21  5:22   ` [PATCH 0/5] arm: set of big endian related fixes for armeb (v7) Victor Kamensky
2014-10-21  7:39 ` Yao Qi
2014-10-22  5:39   ` Victor Kamensky
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='CA+=Sn1mcMzqv14ZMCQN0FcqXXhJ8GHhgiT4cme1JPie-jVxs3g@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=victor.kamensky@linaro.org \
    /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).