From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Change 'len' of to_xfer_partial to ULONGEST
Date: Wed, 08 Jan 2014 12:38:00 -0000 [thread overview]
Message-ID: <52CD46D1.3090006@redhat.com> (raw)
In-Reply-To: <1389166060-434-1-git-send-email-yao@codesourcery.com>
On 01/08/2014 07:27 AM, Yao Qi wrote:
> Hi,
> This patch series is a preparation for the changes mentioned in the
> discussion on changing target_ops method to_xfer_partial [1], in which,
> the expected change would be
>
> LONGEST (*to_xfer_partial) (struct target_ops *ops,
> enum target_object object, const char *annex,
> gdb_byte *readbuf, const gdb_byte *writebuf,
> ULONGEST offset, LONGEST len);
>
> to
>
> enum target_xfer_status (*to_xfer_partial) (struct target_ops *ops,
> enum target_object object, const char *annex,
> gdb_byte *readbuf, const gdb_byte *writebuf,
> ULONGEST offset, ULONGEST len, ULONGEST *xfered_len);
>
> I started from the 'len' "LONGEST -> ULONGEST" transition, and that
> is what this patch series tries to do. This change is quite mechanical.
> Regression tested on x86_64-linux with both native and gdbserver. I
> also rebuilt GDB in the following ways:
>
> - on x86-linux, with all targets enabled,
> - cross build native mingw32,mips-linux,hurd,sparc-linux, gdb on
> linux,
> - build native powerpc-linux gdb on gcc110
> - build spu-elf target on gcc110
> - build aix native gdb on gcc111
> - build native gdb for netbsd on gcc70
>
> There are still some native targets uncovered, such as darwin, but it
> should be easy to fix the build error.
I assume you mean "any build error", as you did touch darwin.
Could be helpful to put this in a test branch to make it super easy
for others to test.
> Patch 2 is major part of this
> series. Patch 3 adjusts linux_common_xfer_osdata and patch 4 adjusts
> two gdbarch methods.
>
> I tried to turn -Wconversion on to help me to check some signed/unsigned
> conversion, but it gives me thousands of errors in a clean build
> (without my patches. Looks signed/unsigned types are used freely in GDB
> code base, so I didn't take much care of signed/unsigned conversion.
>
> I'll finish the interface to_xfer_partial change in next step, and
> adjust its implementations on some targets, such as tfile and ctf
> targets.
>
> [1] supporting all kinds of partially-<unavailable> enum target_object types
> https://sourceware.org/ml/gdb-patches/2013-10/msg00761.html
Thanks a lot for following through with this!
--
Pedro Alves
next prev parent reply other threads:[~2014-01-08 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 7:29 Yao Qi
2014-01-08 7:29 ` [PATCH 4/4] Change 'len''s type from LONGEST to ULONGEST: gdbarch methods core_xfer_shared_libraries and core_xfer_shared_libraries_aix Yao Qi
2014-01-08 12:35 ` Pedro Alves
2014-01-08 7:29 ` [PATCH 1/4] Use target_xfer_partial_ftype for rs6000_xfer_shared_libraries Yao Qi
2014-01-08 7:49 ` Joel Brobecker
2014-01-08 7:29 ` [PATCH 3/4] Change 'len' of linux_common_xfer_osdata to ULONGEST Yao Qi
2014-01-08 12:35 ` Pedro Alves
2014-01-08 7:29 ` [PATCH 2/4] Change to_xfer_partial 'len' type " Yao Qi
2014-01-08 12:34 ` Pedro Alves
2014-01-08 15:31 ` Yao Qi
2014-01-08 12:38 ` Pedro Alves [this message]
2014-01-08 15:29 ` [PATCH 0/4] Change 'len' of to_xfer_partial " Yao Qi
2014-01-14 14:31 ` 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=52CD46D1.3090006@redhat.com \
--to=palves@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).