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

Handle AllocationDefinition and AllocationUsage at export #843

Open
ebausson-obeo opened this issue Nov 6, 2024 · 0 comments
Open

Handle AllocationDefinition and AllocationUsage at export #843

ebausson-obeo opened this issue Nov 6, 2024 · 0 comments

Comments

@ebausson-obeo
Copy link
Contributor

No description provided.

@AxelRICHARD AxelRICHARD added this to the 2025.1.0 milestone Nov 6, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Nov 8, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Nov 8, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Nov 8, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Dec 3, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Dec 3, 2024
ebausson-obeo added a commit to ebausson-obeo/syson that referenced this issue Dec 3, 2024
There are still multiple issue and rules to check, for there are 3 possible syntaxes.

allocate l.component to p.assembly.element;

allocation def Logical_to_Physical :> A {
	end logical : Logical;
	end physical : Physical;
}

allocation allocation2 : Logical_to_Physical allocate (
	logical ::> l,
	physical ::> p
);

The third is the one still raising issue, both in determining its rules and implementing them.
Good luck

Bug: eclipse-syson#843
Signed-off-by: Étienne Bausson <[email protected]>
@AxelRICHARD AxelRICHARD removed this from the 2025.1.0 milestone Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants