From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] i386-tdep.c, i386_process_record, document fall-through case.
Date: Tue, 08 Mar 2011 04:35:00 -0000 [thread overview]
Message-ID: <AANLkTinNQXQWRvk1G8fiXGt1tJXwOGc=BzCDmv_fdf=r@mail.gmail.com> (raw)
In-Reply-To: <4D7527EE.9020204@vmware.com>
I am not sure.
As my poor understanding of C language, break or not break are both OK
for this part.
Thanks,
Hui
On Tue, Mar 8, 2011 at 02:46, Michael Snyder <msnyder@vmware.com> wrote:
> But should there be a break there? Or not?
>
>
>
> Hui Zhu wrote:
>>
>> Hi Michael,
>>
>> Sorry for late.
>>
>> I don't know we need this patch or not.
>>
>> As some people's mail, they don't like this part code. This part
>> should rewrite to share code with opcode or something.
>> So I think in the near future, this code will be rewritten by these
>> guys or somebody else.
>>
>> Thanks,
>> Hui
>>
>> On Sat, Mar 5, 2011 at 03:05, Michael Snyder <msnyder@vmware.com> wrote:
>>>
>>> Michael Snyder wrote:
>>>>
>>>> Hui, is this right?
>>>>
>>>> Thanks,
>>>> Michael
>>>>
>>> Ping? ;-)
>>>
>>>
>
>
next prev parent reply other threads:[~2011-03-08 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 22:34 Michael Snyder
2011-03-02 22:47 ` Mark Kettenis
2011-03-04 19:05 ` Michael Snyder
2011-03-07 9:01 ` Hui Zhu
2011-03-07 19:06 ` Michael Snyder
2011-03-08 4:35 ` Hui Zhu [this message]
2011-03-08 4:54 ` Joel Brobecker
2011-03-08 4:58 ` Hui Zhu
2011-03-08 18:50 ` Michael Snyder
2011-03-08 17:20 ` Tom Tromey
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='AANLkTinNQXQWRvk1G8fiXGt1tJXwOGc=BzCDmv_fdf=r@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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