[Bug 1001607] Cortex-M4F architectural Floating Point Support

[bugzilla-daemon@bugs.ecos.sourceware.org]

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

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

--- Comment #56 from Ilija Kocho <ilijak@siva.com.mk> ---
Created attachment 2092
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2092&action=edit
Improve code build flag control - incremental to attachment 2082

Jifl

Here is a small patch (increment to attachment 2082) that eliminates the need
for compiler related changes (that were intended for switch to GCC 4.6).
Consequently the big comment together with commented pieces of code are gone.

Briefly, now if CYGHWR_HAL_CORTEXM == "M4"
 - FPU disable is permissible to both cortex-m3 and cortex-m4 so user can  
manually select either, just like in present CVS.
 - FPU enable enforces exclusion of cortex-m3 and inclusion of cortex-m4.
Subsequent FPU disable will not revert cortex-m3. The side effect is that 2
consecutive clicks will set build flags for Cortex-M4.

If CYGHWR_HAL_CORTEXM == "M4"
(manual) placement of -mcpu=cortex-m4 causes conflict

Now we can keep current default flags provided by platforms as are, even when
we switch to new compiler, though nothing can stop us to change them if we see
fit. 

Jifl,
With this I think we are go for commit. If you don't have objections I would
commit, some night during second half of next week (including the weekend) -
before Embedded World.

Ilija

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