-
Notifications
You must be signed in to change notification settings - Fork 81
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
Switch to gcc 6.3 as minimum requirement? #17
Comments
I think the ease of access to the Raspbian image, and the supported hardware ( I have an original Raspberry Pi which it runs on ) I personally think it's a yes. |
Just a quick questions to anyone who has more experience with gcc-versions and targets than I have. |
@doe300
In this case, we care support for march |
My cross-rpi repo is obsolete, so please use our new one: https://github.com/Idein/docker-cross-rpi |
@nomaddo linaro's arm toolchain lacks support for armv6 itself, not vfp... |
@Terminus-IMRC very thanks for the correction :) |
After some investigations, it turned out that cross toolchain of Linaro and Debian both support armv6 (VFP) and armv7 (NEON), which means that you can just switch to use |
Currently, VC4C and VC4CL are held compatible with the ancient GCC 4.8 to support older Raspbian systems. GCC 4.8 barely supports C++11 [1] and hence lacks a lot of useful new features provided in C++14 and C++17. The latest Raspian Stretch ships with GCC 6.3, which completely supports C++14 as well as a lot of C++17 features [1].
Some useful C++14/C++17 features we could use when switching [1]:
__has_include
e.g. for distinguishing LLVM versionsstring_view
, file-system support,optional
andany
in experimental namespaceSince the official raspberrypi-tools repository has not yet been upgraded to GCC 6.3 (see here), we would need to use another tool-chain for our CircleCI cross-compilation such as this one (see also here).
So the question is:
Should we drop support for GCC 4.8 and therefore for older Raspbian systems?
[1] https://gcc.gnu.org/projects/cxx-status.html
The text was updated successfully, but these errors were encountered: