From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [RFA] i386-tdep.c: fix a bug in prec i386 code
Date: Thu, 04 Mar 2010 07:58:00 -0000 [thread overview]
Message-ID: <daef60381003032358v562137b3kb8d492881355c508@mail.gmail.com> (raw)
In-Reply-To: <20100304073855.GK2832@adacore.com>
On Thu, Mar 4, 2010 at 15:38, Joel Brobecker <brobecker@adacore.com> wrote:
>
> > 2010-03-04 Hui Zhu <teawater@gmail.com>
> >
> > * i386-tdep.c (i386_process_record): Change "addr" to "tmpu64".
>
> OK.
Checked in.
>
> As an aside, your code needs a really good thorough cleanup. I warned
> you already about the use of variables with a meaningless name, and
> you'll make this sort of mistake again for as long as you keep using
> them. However, my main point is that the use of a giant switch statement
> makes your code very hard to read and review. I really suggest that
> you create a new file, precord-i386.c where you put your stuff there,
> and instead of inlining the code inside each case, you define small
> contained procedures for each instruction (or instruction group).
> It'll be easier to find the code that handles such and such instruction,
> easier to write a ChangeLog entry that tells us more about where the
> change was made, and it'll make the switch block actually possible
> to read.
>
Agree with you.
But prec patch have some still hang in there (see
http://sourceware.org/gdb/wiki/ProcessRecord) and this change will be
very big.
If I do it, what I will meet is:
1. Make a patch follow the hang change, then the new patch cannot
checked in before the hang patch in.
2. Make a patch just for cvs-head. After this patch in, this hang
patch need update follow cvs-head. This is not a small work.
I conflict with them. So ...
Thanks,
Hui
prev parent reply other threads:[~2010-03-04 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 2:37 Hui Zhu
2010-03-04 7:39 ` Joel Brobecker
2010-03-04 7:58 ` Hui Zhu [this message]
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=daef60381003032358v562137b3kb8d492881355c508@mail.gmail.com \
--to=teawater@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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