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

✨ Add relaxed_message #673

Merged
merged 1 commit into from
Jan 8, 2025
Merged

✨ Add relaxed_message #673

merged 1 commit into from
Jan 8, 2025

Conversation

elbeno
Copy link
Contributor

@elbeno elbeno commented Jan 8, 2025

Problem:

  • Developing message formats is onerous; we'd like the compiler to take care of packing messages until we know exactly where to put fields.

Solution:

Note:

  • All auto-located fields are put after the fixed spec fields.
  • Auto-located fields are sorted from largest to smallest to ease alignment.

Closes #664

Problem:
- Developing message formats is onerous; we'd like the compiler to take care of
  packing messages until we know exactly where to put fields.

Solution:
- Add `relaxed_message` as in intel#664

Note:
- All auto-located fields are put after the fixed spec fields.
- Auto-located fields are sorted from largest to smallest to ease alignment.
Copy link
Contributor

@mjcaisse-intel mjcaisse-intel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a nice addition!

@bdeane-intel bdeane-intel merged commit 1164ca7 into intel:main Jan 8, 2025
22 checks passed
@elbeno elbeno deleted the auto-message branch January 8, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

msg::relaxed_message: Add a msg type that lets one or more field locations be allocated automatically
3 participants