-
Notifications
You must be signed in to change notification settings - Fork 15
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
Ada 2022 support in gnat_arm_elf #69
Comments
Hello @dinkelk, the embedded runtimes do not support all the features of Ada. |
Hi @Fabien-Chouteau. I do understand that, but I guess that it is just a bummer that this code compiles fine without the Thank you for replying. |
Sorry I didn't understand that. Can you send a small piece of code and gpr file that shows the problem. |
@Fabien-Chouteau - I created a minimal example here: https://github.com/dinkelk/embedded_ada_2022_test If you run |
Hi @dinkelk, so the issue here is with a task or protected object as field of a record when using an We might do another release to fix this, in the meantime you can copy those two files: s-putaim.ads, s-putaim.adb in the the |
@Fabien-Chouteau - Thank you! Copying the files has fixed my issue. |
This applies a temporary fix to the embedded-rpi-pico runtime installed with the Adamant example repository. It fixes: alire-project/GNAT-FSF-builds#69 to allow for compilation with the -gnat2022 flag until a new release of gnat_arm_elf is available, ie. https://alire.ada.dev/crates/gnat_arm_elf. This will likely be fixed in some version >14.1.3 and this temporary fix can be reverted.
I am not sure if this it the right place to ask this, so please redirect if needed.
I tried to enable the
-gnat2022
flag in a project I am working on that uses theembedded-rpi-pico
runtime supplied in thegnat_arm_elf
Alire crate. However, when doing so I get many compiler errors like:It seems like
s-putaim.ads
is not yet included in the arm tasking/embedded runtimes? Is this expected? Is Ada 2022 support going to arrive for the arm runtimes in the future? Thanks!The text was updated successfully, but these errors were encountered: