Skip to content

C99/C++98 standard compliance #2154

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.

Sign up for GitHub

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

Jump to bottom
Closed
9 tasks
geky opened this issue Jul 12, 2016 · 1 comment
Closed
9 tasks

C99/C++98 standard compliance #2154

geky opened this issue Jul 12, 2016 · 1 comment

Comments

@geky
Copy link
Contributor

geky commented Jul 12, 2016 •
edited
Loading

Currently, there are no barriers in place for using compiler extensions. This makes it difficult to know when code is inherently unportable. Allowing compiler extensions hurts reproducibility across toolchains.

From previous discussions these appear to be our target standards:

  • C99
  • C++98 (C++11 is unsupported in IAR)

Here is a quick checklist of what is needed to bring mbed up to compliance:

  • strict c99/c++98 flags in gcc
  • strict c99/c++98 flags in armc5
  • strict c99/c++98 flags in iar
  • compile in gcc
  • compile in armc5
  • compile in iar
  • warning free in gcc
  • warning free in armc5
  • warning free in iar

Previous issue: #241
@geky geky changed the title Language standard compliance C99/C++98 standard compliance Jul 12, 2016
@geky
Copy link
Contributor Author

geky commented Jul 12, 2016

Sorry for the redundant issues, I got confused by github site problems.

#2152

@geky geky closed this as completed Jul 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@geky