From: Joel Brobecker <brobecker@adacore.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Michael Snyder <msnyder@vmware.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA/i386] Prec x86 MMX 3DNow! SSE SSE2 SSE3 SSSE3 SSE4 support
Date: Mon, 11 Jan 2010 04:05:00 -0000 [thread overview]
Message-ID: <20100111040452.GA30569@adacore.com> (raw)
In-Reply-To: <daef60381001101847w795c64eds8258cb4993f3c542@mail.gmail.com>
> I am not sure it better can be the part of this patch. It doesn't
> have relationship with sse insn support, right?
This is why I said that this could be done in a followup patch.
> Looks you have a lot of idea on it. I suggest you can work on it. :)
Sorry, I have no interest at this point in time in working on the process
record support. I am, however, spending a very large amount of time trying
to review your code, provide comments, and answering your emails.
The suggestion about fixing the way you handle errors, in particular
the use of labels, is an important one, so please do not discard it
on the basis that someone else can work on it.
> + switch (tmpu8)
>
> Im not sure it clear or not. I think add more vals will make the code
> not clear.
I think you are wrong, but we can only know by comparing the two
alternatives. Your code is using switch statements inside switch
statements, and this allows this type of practice. But if it was me,
I would have asked for each case block that requires non-trivial
processing to be moved to a separate function. With that in mind,
you'd have had to declare a new variable instead of reusing a generic
one which has a meaningless name. In the present case, you can
certainly declare a variable local to where you need it. For instance:
case bla:
{
int regno;
target_read_memory (addr, ®no);
[...]
This code looks a lot clearer to me than:
case bla:
target_read_memory (addr, &tmpu);
That being said, this is not the most important part in the list of
things I'd like to see being improved in the process record code.
So, in the grand scheme of things, I'm fine if you are still not
convinced.
--
Joel
next prev parent reply other threads:[~2010-01-11 4:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 15:00 [RFA] " Hui Zhu
2009-12-07 16:54 ` Michael Snyder
2009-12-07 17:16 ` Michael Snyder
2009-12-07 17:43 ` Joel Brobecker
2009-12-07 17:54 ` Michael Snyder
2009-12-07 18:00 ` Joel Brobecker
2009-12-07 18:05 ` Michael Snyder
2009-12-08 5:51 ` Hui Zhu
2009-12-08 19:56 ` Michael Snyder
2009-12-07 18:08 ` Doug Evans
2009-12-08 17:43 ` Tom Tromey
2009-12-10 19:52 ` Michael Snyder
2009-12-11 15:00 ` Hui Zhu
2009-12-13 4:28 ` Hui Zhu
2009-12-13 10:35 ` Hui Zhu
2009-12-14 18:24 ` Michael Snyder
2009-12-15 1:47 ` Hui Zhu
2009-12-18 19:44 ` Michael Snyder
2010-01-08 16:07 ` Hui Zhu
2010-01-08 18:45 ` Michael Snyder
2010-01-09 12:28 ` [RFA/i386] " Joel Brobecker
2010-01-11 2:48 ` Hui Zhu
2010-01-11 4:05 ` Joel Brobecker [this message]
2010-01-12 1:38 ` Michael Snyder
2010-03-28 16:27 ` Hui Zhu
2010-03-29 1:35 ` Michael Snyder
2010-03-29 1:36 ` Michael Snyder
2010-03-29 9:25 ` Hui Zhu
2010-03-29 1:40 ` Michael Snyder
2010-03-29 2:23 ` Hui Zhu
2010-03-29 13:21 ` Hui Zhu
2010-03-29 17:52 ` Michael Snyder
2010-03-29 18:11 ` Michael Snyder
2010-03-30 6:29 ` Hui Zhu
2010-03-30 12:55 ` Hui Zhu
2010-04-01 15:36 ` Hui Zhu
2010-04-01 21:50 ` Michael Snyder
2010-04-02 5:14 ` Hui Zhu
2010-03-29 2:18 ` Michael Snyder
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=20100111040452.GA30569@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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