> -----Original Message-----
> From: Ralph Lange [mailto:[email protected]]
>
> is that true for all target architectures or just for
> the PPC arch that
> Dirk is seeing this on?
>
The WRS warnings concerning this issue are in an
architecture independent section of the documentation,
and I don't see anything specific on this issue in the
PPC specific section of the vxWorks 5.4 documentation.
A potential pitfall might be that the PPC compiler used
the FP registers to pass integer parameters, and that
the user's ISR didn't anticipate that scenario.
Jeff
>
>
> Jeff Hill wrote:
>
> >Dirk,
> >
> >I don't know if anyone has made this suggestion, but
> >watch out for a driver that uses floating point in
> its
> >interrupt service routines as, on vxWorks, the FP
> >register contents are not saved / restored when
> entering
> >/ exiting interrupt context. The driver must do this
> >manually if it finds a need to use FP in its ISR.
> >
> >Jeff
> >
> >
- Replies:
- Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? J. Frederick Bartlett
- References:
- Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Ralph Lange
- Navigate by Date:
- Prev:
Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Ralph Lange
- Next:
Browsing the ioc error log file Ned Arnold
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Ralph Lange
- Next:
Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? J. Frederick Bartlett
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|