-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCC compiler option should include '-mcpu=hs38' for HSDK #31757
Comments
@abrodkin FYI |
We do plan to address that, but the idea was to do it for the v2.6 to not add more troubles in yet stabilized v2.5. |
I do have a WA for this by patching the GCC cmake file, so no critical. As for the support of HSDK with MW toolchain (#30162) that you mentioned, would this be available for 2.5., or only in 2.6? |
@jacoba-at since we're talking about an issue in libs bundled with MW toolchain it doesn't have any direct connection with a Zephyr release, instead it has to do with MW toolchain release. That said if this atomics problem gets fixed in the next release 2021.03 of MW tools, then you'll be able to use that newer MW version with Zephyr 2.5 as well as with 2.6 etc. In the meantime I'd strongly suggest you to file a formal customer case via Synopsys Solvnet (https://solvnet.synopsys.com) to add more visibility to our engineering team referring to #30162. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Please remove the stale label. |
@jacoba-at just FYI we do remember about adding So stay tuned and I hope to get this one addresses soon as well and do that right before v2.6 code freeze later this May. |
@jacoba-at please see #35415, instead of -mcpu=hs38 that uses -mcpu=archs, which has the same effect. |
Looks good to me, thanks.
-Jacob
…On Wed, May 26, 2021 at 12:02 PM ruuddw ***@***.***> wrote:
@jacoba-at <https://github.com/jacoba-at> please see #35415
<#35415>, instead of
-mcpu=hs38 that uses -mcpu=archs, which has the same effect.
ok to close this once that PR gets merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31757 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH4FZDSMJJYXTDYPHJ42SBTTPS2I7ANCNFSM4WXNQGTA>
.
--
*Jacob Avraham **| Principal SW Engineer*
*M: +972-52-6970067 | T: +972-9-8865314*
*E: ***@***.*** ***@***.***>*
*Grand Netter building, Kfar Netter, Israel*
*Autotalks* | www.auto-talks.com
|
Describe the bug
When building Zephyr for the HSDK board, it passed to gcc the option '-mcpu=hs'. This creates code that misses some processor functionality. For example if you use modulo C operator (a % b), it calls a function to perform this operation, instead of using the 'REM' assembly instruction.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect to see '-mcpu=hs38' and not 'mcpu=hs'
Impact
I ran a test that uses heavily the modulo operator and it ran x4 slower without the -mcpu=hs38 flag.
Environment (please complete the following information):
Additional context
How can I add more flags or override some to the zephyr compilation? I tries adding zephyr_cc_option() to my application CMakeLists.txt , but didn't effected to compilation flags.
The text was updated successfully, but these errors were encountered: