From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH v2] Expand bitpos and type.length to LONGEST and ULONGEST
Date: Wed, 23 May 2012 13:52:00 -0000 [thread overview]
Message-ID: <20120523192245.0f785e69@spoyarek> (raw)
In-Reply-To: <20120515200454.GA11338@host2.jankratochvil.net>
Hi Jan,
I'm back to working on this. A couple of clarifications on the review:
> > static void
> > -copy_bitwise (gdb_byte *dest, unsigned int dest_offset_bits,
> > - const gdb_byte *source, unsigned int
> > source_offset_bits,
> > - unsigned int bit_count,
> > +copy_bitwise (gdb_byte *dest, ULONGEST dest_offset_bits,
> > + const gdb_byte *source, ULONGEST source_offset,
> > + ULONGEST bit_count,
> > int bits_big_endian)
> > {
> > - unsigned int dest_avail;
> > + unsigned int dest_avail, source_offset_bits;
> > int datum;
> >
> > /* Reduce everything to byte-size pieces. */
> > dest += dest_offset_bits / 8;
> > dest_offset_bits %= 8;
> > - source += source_offset_bits / 8;
> > - source_offset_bits %= 8;
> > + source += source_offset / 8;
> > + source_offset_bits = source_offset % 8;
>
> I do not fully understand this whole change but it looks unrelated to
> this patch to me.
I had to split up the source_offset and source_offset bits because
source_offset can be LONGEST but the bits would always be less than 8.
I did this because otherwise I would have had to change signatures of
functions that use source_offset_bits even when it is not really needed
(extract_bits and extract_bits_primitive).
> > size of this argument and rounding to an int boundary. */
> > diff --git a/gdb/symfile-mem.c b/gdb/symfile-mem.c
> > index 91125e1..a3c15d0 100644
> > --- a/gdb/symfile-mem.c
> > +++ b/gdb/symfile-mem.c
> > @@ -55,6 +55,11 @@
> > #include "auxv.h"
> > #include "elf/common.h"
> >
> > +static int symfile_target_read_memory (CORE_ADDR memaddr, gdb_byte
> > *myaddr,
> > + int len)
> > +{
> > + return target_read_memory (memaddr, myaddr, len);
> > +}
>
> Formatting should be (see also tab -> 2 spaces):
>
> static int
> symfile_target_read_memory (CORE_ADDR memaddr, gdb_byte *myaddr, int
> len) {
> return target_read_memory (memaddr, myaddr, len);
> }
>
> But I proposed to rather target_read_memory use size_t and we should
> then proposed to bfd/ that it also uses size_t for
> bfd_elf_bfd_from_remote_memory.
Perhaps it will be helpful if I keep this change (and consequently the
rest of the read/write_memory function changes) as a separate patch?
AFAICT the only place where not having these changes as part of the
original patch will potentially cause problems is in
do_search_struct_field. That way I'll also do the size_t changes right
away instead of changing and then reverting the change.
> > void
> > modify_field (struct type *type, gdb_byte *addr,
> > - LONGEST fieldval, int bitpos, int bitsize)
> > + LONGEST fieldval, LONGEST bitpos, unsigned int
> > bitsize)
>
> WHy to make bitsize unsigned here?
It's a minor nit to make the arguments match the comment above it:
Requires 0 < BITSIZE <= lbits, 0 <= BITPOS % 8 + BITSIZE <= lbits, and
0 <= BITPOS, where lbits is the size of a LONGEST in bits. */
but this does not belong in this patch. I'll have to get together these
smaller patches too so that they're not missed out.
I'm still working on the rest of the points, which is mainly maintain
signedness when expanding variables and a couple of other problems.
Regards,
Siddhesh
next prev parent reply other threads:[~2012-05-23 13:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 14:53 [PATCH] Expand bitpos to LONGEST to allow access to large offsets within a struct Siddhesh Poyarekar
2012-02-21 20:46 ` Tom Tromey
2012-02-22 7:44 ` Siddhesh Poyarekar
2012-02-29 13:55 ` Siddhesh Poyarekar
2012-02-29 13:59 ` Siddhesh Poyarekar
2012-03-01 22:45 ` Jan Kratochvil
2012-03-05 6:34 ` Siddhesh Poyarekar
2012-03-05 8:05 ` Jan Kratochvil
2012-03-21 10:06 ` [PATCH] Allow 64-bit enum values Siddhesh Poyarekar
2012-03-27 17:00 ` Jan Kratochvil
2012-03-28 4:19 ` Siddhesh Poyarekar
2012-03-30 16:15 ` Jan Kratochvil
2012-04-17 14:01 ` Jan Kratochvil
2012-04-18 2:53 ` Siddhesh Poyarekar
2012-04-18 6:58 ` [commit] " Jan Kratochvil
2012-04-18 7:06 ` [ChangeLog commit] " Jan Kratochvil
2012-04-19 16:58 ` [commit] " Ulrich Weigand
2012-04-20 4:23 ` Siddhesh Poyarekar
2012-04-20 7:50 ` [obv] Fix python-2.4 compilation compat. [Re: [commit] [PATCH] Allow 64-bit enum values] Jan Kratochvil
2012-04-20 19:00 ` Tom Tromey
2012-03-28 16:55 ` [PATCH] Allow 64-bit enum values Tom Tromey
2012-03-29 10:56 ` Siddhesh Poyarekar
2012-04-17 13:11 ` [commit] Support 64-bit constants/enums on 32-bit host [Re: [PATCH] Allow 64-bit enum values] Jan Kratochvil
2012-04-17 13:16 ` [patch!] " Jan Kratochvil
2012-04-17 14:33 ` [patch] " Jan Kratochvil
2012-04-17 15:59 ` Tom Tromey
2012-04-17 15:42 ` Jan Kratochvil
2012-04-17 15:52 ` Tom Tromey
2012-04-17 14:33 ` [commit] " Tom Tromey
2012-04-17 14:55 ` Jan Kratochvil
2012-04-17 15:18 ` Tom Tromey
2012-04-17 15:32 ` Jan Kratochvil
2012-04-17 19:32 ` Jan Kratochvil
2012-04-17 20:51 ` Tom Tromey
2012-04-18 7:01 ` [real commit] " Jan Kratochvil
2012-02-21 21:39 ` [PATCH] Expand bitpos to LONGEST to allow access to large offsets within a struct Jan Kratochvil
2012-05-04 13:10 ` [PATCH v2] Expand bitpos and type.length to LONGEST and ULONGEST Siddhesh Poyarekar
2012-05-15 9:46 ` ping: " Siddhesh Poyarekar
2012-05-15 9:49 ` Jan Kratochvil
2012-05-15 10:02 ` Siddhesh Poyarekar
2012-05-15 20:07 ` Jan Kratochvil
2012-05-16 3:50 ` Siddhesh Poyarekar
2012-05-16 7:19 ` Jan Kratochvil
2012-05-16 7:41 ` Siddhesh Poyarekar
2012-05-20 15:43 ` Doug Evans
2012-05-20 20:24 ` Jan Kratochvil
2012-05-20 20:28 ` Doug Evans
2012-05-23 13:52 ` Siddhesh Poyarekar [this message]
2012-05-23 17:46 ` Jan Kratochvil
2012-05-24 1:36 ` Siddhesh Poyarekar
2012-05-24 15:01 ` Jan Kratochvil
2012-05-31 18:15 ` [PATCH v3] " Siddhesh Poyarekar
2012-06-05 22:27 ` Jan Kratochvil
2012-06-06 18:23 ` Siddhesh Poyarekar
2012-06-06 21:34 ` Jan Kratochvil
2012-06-08 14:16 ` Jan Kratochvil
2012-06-08 15:27 ` Jan Kratochvil
2012-06-11 12:53 ` Siddhesh Poyarekar
2012-06-11 13:00 ` Jan Kratochvil
2012-06-11 18:33 ` Siddhesh Poyarekar
2012-06-12 9:56 ` Jan Kratochvil
2012-06-12 14:35 ` Jan Kratochvil
2012-06-18 10:31 ` [1/2][PATCH " Siddhesh Poyarekar
2012-06-20 15:47 ` Jan Kratochvil
2012-06-20 16:32 ` Siddhesh Poyarekar
2012-06-20 17:25 ` Jan Kratochvil
2012-06-23 1:59 ` Siddhesh Poyarekar
2012-06-18 10:31 ` [2/2][PATCH " Siddhesh Poyarekar
2012-05-31 6:39 ` [PATCH v2] " Siddhesh Poyarekar
2012-05-31 9:24 ` Siddhesh Poyarekar
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=20120523192245.0f785e69@spoyarek \
--to=siddhesh@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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