[Bug 1001607] Cortex-M4F architectural Floating Point Support

[bugzilla-daemon at bugs dot ecos dot sourceware dot org]

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001607

Ilija Kocho <ilijak@siva.com.mk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #1991|0                           |1
        is obsolete|                            |
   Attachment #2074|0                           |1
        is obsolete|                            |
   Attachment #2076|0                           |1
        is obsolete|                            |

--- Comment #50 from Ilija Kocho <ilijak@siva.com.mk> ---
Created attachment 2078
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2078&action=edit
Cortex-M4F Floating Point Support 130207

Jifl

Here is a patch with CYGARC_CORTEXM_FPU_EXC_AUTOSAVE option removed.
CYGARC_CORTEXM_FPU_EXC_AUTOSAVE still lives as a macro defined in
fpv4_sp_d16.h.

Some notes:

Tests, included in this patch are general. The only Cortex-M depndent code is
HAL_CLOCK_READ_NS() that can be conditionaly replaced with HAL_CLOCK_READ() for
other architectures. Then we can consider placing these tests in kernel or
hal/common.

Speaking of HAL_CLOCK_READ_NS(), is it desirable for inclusion in cortex-m
headers?

And to continue with our off topic: I would go with CYGBLD_FORCE_INLINE if you
don't object, what is your opinion?

Ilija

-- 
You are receiving this mail because:
You are on the CC list for the bug.