-
-
Notifications
You must be signed in to change notification settings - Fork 725
Update release version of arm-none-eabi-gcc #290
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
Comments
Seconded. 4.8.3 is ridiculously old and some software (eg, FreeRTOS 10) won't build with it. |
I think this one can be closed in favor of #313 (which requests the same, but has a bit more discussion already). |
Closing ad duplicate and tracking on #313 , staging packages are due to be available later today. |
By adding http://downloads.arduino.cc/packages/package_samd_newtoolchain_index.json you can test the latest toolchain; please test and report any error you may encounter, thanks! |
Ok, first feedback. Getting lots of warning about use of #if. See discussion about this that the webkit people had here: https://bugs.webkit.org/show_bug.cgi?id=167643 Two options.
Option 2 may be difficult as a lot of the warning are coming from CMSIS which comes from the Atmel ASF. The warning seems overly pedantic, and so it seems reasonable to globally suppress it. Warning look like this (ad nauseam):
|
@stevenj yes, it's a known issue (see #313 (comment)). Please continue the discussion there so we don't split up the topic 😛 |
Fixes arduino#287 The warnings look like: ``` Line 338 Char 37 warning: 'void* memcpy(void*, const void*, size_t)' writing to an object of type 'struct DmacDescriptor' with no trivial copy-assignment [-Wclass-memaccess] ```
Arduino currently provides arm-none-eabi-gcc tool version 4.8.3 .
This version is very old and is no longer distributed at arm.com .
If the compiler were upgraded to at least version 6, then modern c++ tools like boost::hana could be used.
This issue was moved from arduino/Arduino#7088 . I understand upgrading the toolchain could be a big effort because it needs to be validated again. It would be great to have a note regarding what this validation process is, in case collaborators could help.
The text was updated successfully, but these errors were encountered: