Fix ARMC6 fpu detection for M33 core

[orenc17]

Description

normal Coretex-M33 was not adding -mfpu=none to the build command
this issue was caused by #10390

This fix is needed for #9221

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@kjbracey-arm @ARMmbed/mbed-os-maintainers

Release Notes

[kjbracey]

Looking at this, I note the M33E (DSP but no FP) addition from #10390 (744e2cc) is missing a bit for ARMC6; it didn't get added to the cpu lookup table above for the compiler, and it would need to be added to the line you're fixing too.

It would be handy if you could fix that at the same time, otherwise, I'll fix it later.

[0xc0170]

I was quick to start CI, if updated, @orenc17 let us know, we restart CI

[alzix]

I was quick to start CI, if updated, @orenc17 let us know, we restart CI

please do

[kjbracey]

Ta, but the cpu table above is also missing the entry "Cortex-M33E": "cortex-m33",

[mbed-ci]

Test run: FAILED

Summary: 6 of 7 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_mbed2-build-ARM
• jenkins-ci/mbed-os-ci_build-IAR
• jenkins-ci/mbed-os-ci_mbed2-build-GCC_ARM
• jenkins-ci/mbed-os-ci_build-GCC_ARM
• jenkins-ci/mbed-os-ci_build-ARM
• jenkins-ci/mbed-os-ci_mbed2-build-IAR

[0xc0170]

Aborted, will restart once reviewed again

[orenc17]

@0xc0170 ready for CI

[0xc0170]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts