From: Thomas Monjalon <thomas_ml@monjalon.net>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-ppc: exception model of 603e inherits from 603
Date: Mon, 26 Apr 2010 11:47:55 +0200 [thread overview]
Message-ID: <201004261147.55190.thomas_ml@monjalon.net> (raw)
In-Reply-To: <06CE1285-856D-449A-A296-66621006EA70@web.de>
Andreas Färber wrote:
> Am 23.04.2010 um 11:44 schrieb Thomas Monjalon:
> > It appears that the exception handling of 603e is the same as 603.
> > So it could be removed safely.
>
> Are you referring to some ppc manual or to the current code base?
I'm referring to the current code base.
I don't think there is a difference of exception handling between these two
processors. So I think it's better to factorize the code and to refork it if
a difference is needed one day. But I think we need to minimize special
handling cases.
--
Thomas
prev parent reply other threads:[~2010-04-26 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 9:44 [Qemu-devel] [PATCH] target-ppc: exception model of 603e inherits from 603 Thomas Monjalon
2010-04-24 12:48 ` Andreas Färber
2010-04-26 9:47 ` Thomas Monjalon [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=201004261147.55190.thomas_ml@monjalon.net \
--to=thomas_ml@monjalon.net \
--cc=andreas.faerber@web.de \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).