[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PowerPC Exceptions: Raw Exception API
- Date: Thu, 18 Dec 2008 02:00:45 -0800
- From: strauman at slac.stanford.edu (Till Straumann)
- Subject: PowerPC Exceptions: Raw Exception API
I kind of agree but I also think that it might
still be useful to maintain the current API's
feature to let the user install a handler
at the lowest level (by patching the vector
as it is done now). I would not object to
changing the implementation, though, if
that helps reducing the table size (which
for my platforms is not an issue).
Sebastian Huber wrote:
> the current PowerPC Exception API is defined in:
> In has the capability to invoke special on and off functions whenever a
> handler is connected or disconnected. Unfortunately this requires non
> constant memory space. Currently a static table is used and it demands
> 896 Bytes. This is to much for systems with a small memory.
> The features of this API are not used. The API is used in
> This file is deprecated. See
> We should consider to remove these files in the CVS HEAD.
> BSPs that use the API to install exception handler code:
> o score603e
> o mpc8260ads
> o mbx8xx
> It should be easy to modify them if the API changes. I want to remove
> the existing API and replace it with something that requires no non
> constant memory. It will allow the installation of exception handlers
> based on the existing category infrastructure.