You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
issue#1937 deals with not processing subprogram access . parameter.
For this one I put in an errata for V2.2 (saeaadl/aadlv2.2#39).
The justification for also allowing just a reference to the subprogram access is that the subprogram may not have an in parameter but an out parameter (or vice versa). So in one direction we could not point to a parameter.
Ok.
John Hudak is doing some modeling with remote subprogram calls for his IDT work. That's what triggered the sequence of issues. Issues 1937 and 1941 are more relevant at this time.
lwrage
changed the title
OSATE incorrectly marks flow specs involving subprogram access as error
Subprogram access features should be allowed as flow specification ends
Aug 15, 2019
The standard allows flow end point to be subprogram access.
This implements saeaadl/aadlv2.2#39
The text was updated successfully, but these errors were encountered: