Skip to content
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

Support new versions of GNAT #1116

Closed
jklmnn opened this issue Jul 25, 2022 · 0 comments · Fixed by #1117
Closed

Support new versions of GNAT #1116

jklmnn opened this issue Jul 25, 2022 · 0 comments · Fixed by #1117
Assignees
Labels

Comments

@jklmnn
Copy link
Member

jklmnn commented Jul 25, 2022

Newer versions of GNAT require generic parameters to be marked as Ghost if they're ghost subprograms. If a ghost function is passed as a generic parameter, previously it had been done the same way as with a regular function:

generic
   with function Some_Ghost_Function return Boolean;
package Some_Package is

With newer GNAT versions such a parameter has to be explicitly marked as Ghost:

generic
   with function Some_Ghost_Function return Boolean with Ghost;
package Some_Package is

This behaviour is a problem in RecordFlux in the RFLX.RFLX_Message_Sequence package as the function Element_Initialized is usually ghost. Adding with Ghost would solve the problem but also breaks compatibility with older compilers. The fix here is to remove the Ghost aspect from the Initialized function of messages.

@jklmnn jklmnn added the bug label Jul 25, 2022
@jklmnn jklmnn self-assigned this Jul 25, 2022
jklmnn added a commit that referenced this issue Jul 25, 2022
jklmnn added a commit that referenced this issue Jul 25, 2022
senier pushed a commit that referenced this issue Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant