From: Michael Eager <eager@eagerm.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] bitpos: Expand type_field_bitpos to LONGEST and type.length to ULONGEST
Date: Sun, 05 Aug 2012 11:42:00 -0000 [thread overview]
Message-ID: <501E5C33.1020808@eagerm.com> (raw)
In-Reply-To: <20120805005359.2dc3edc0@spoyarek>
On 08/04/2012 12:23 PM, Siddhesh Poyarekar wrote:
> Hi,
>
> This is the main patch that expands bitpos and type.length to LONGEST
> and ULONGEST respectively. The change from the earlier patch is that I
> have identified additional expansions based on the splint report and I
> have reverted the expansion in the LEN argument for insert/remove
> watchpoints since it's not necessary.
The ChangeLog mentions a modification to microblaze-tdep.c, but the
patch does not contain any changes to this file.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2012-08-05 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 19:25 Siddhesh Poyarekar
2012-08-05 11:42 ` Michael Eager [this message]
2012-08-06 3:07 ` Siddhesh Poyarekar
2012-08-06 14:13 ` Michael Eager
2012-08-22 17:15 ` Sergio Durigan Junior
2012-08-22 20:41 ` Sergio Durigan Junior
2012-08-23 10:54 ` 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=501E5C33.1020808@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@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