-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix detection of supported targets for mbed 2 builds #10347
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
Conversation
@bridadan, thank you for your changes. |
CI started |
Test run: FAILEDSummary: 1 of 9 test jobs failed Failed test jobs:
|
Looking at the build failures, only SAM targets failed Mbed 2 ARMC5 build. Please review |
Looks like those targets aren't compatible with ARMC6, so I moved them to ARMC5 only. |
CI started |
Test run: FAILEDSummary: 1 of 7 test jobs failed Failed test jobs:
|
The hal code for this target uses "const volatile" types inside of structs, which are non-trivially copyable in clang (used by ARMC6). This causes the build to fail. Here's the commit that changed this in clang: llvm-mirror/clang@a3d727b It seems this was reverteed some time ago in clang, but ARMC6 may not be up to date.
ec49777
to
11775ef
Compare
Oh jeez, I missed one. Pushed a fix. |
rabble rabble rabble |
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@jeromecoutant Mind taking a look at this? |
Description
Fix #10107.
This should get Mbed 2 builds going again with ARMC6. The uARM logic doesn't seem to be 100%, but honestly I'm not really sure what the expected behavior is for it.
Pull request type
Reviewers
Release Notes
@jeromecoutant