Subject: |
Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? |
From: |
Dirk Zimoch <[email protected]> |
To: |
Kay-Uwe Kasemir <[email protected]>, "'EPICS Tech Talk'" <[email protected]> |
Date: |
Thu, 10 Feb 2005 15:15:37 +0100 |
Kay-Uwe Kasemir wrote:
Hello:
Having learned the hard way,
I'm now quite aware of the VX_FP_TASK option
for vxWorks' taskCreate().
To be save inside ISR code, no matter how the compiler
optimizes your non-floating point code:
Are there vxWorks subroutines or asm(...)-type macros that allows
me to save/restore the FP registers?
If not, does anybody know the asm(..) lines that would work on
a PPC CPU?
There are:
fppSave() and fppRestore()
But I still don't believe that this is my problem.
Im doing further tests.
Dirk
--
Dr. Dirk Zimoch
Swiss Light Source
Paul Scherrer Institut
Computing and Controls
phone +41 56 310 5182
fax +41 56 310 4413
- References:
- RE: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Jeff Hill
- Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? J. Frederick Bartlett
- Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
Re: compiler bug in gcc version 2.8.1 (Tornado1) for PPC corrupts floationg point constants? Kay-Uwe Kasemir
- Next:
Re: Browsing the ioc error log file Brian McAllister
- 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? Kay-Uwe Kasemir
- 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
|