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

Removed LV_ATTRIBUTE_FAST_MEM function attribute from prototypes and kept only on function declarations or static inline functions #5467

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

ktand
Copy link
Contributor

@ktand ktand commented Jan 24, 2024

Description of the feature or fix

Removed LV_ATTRIBUTE_FAST_MEM function attribute from prototypes and kept only on function declarations and static inline functions.

This fixes an issue in ESP-IDF where section attributes use COUNTER macro, and this results in prototype and declaration having different sections assigned

This was previously fixed in the 8.x release.

See #4391 and #4404

…kept only on function declarations or static inline functions

This fixes an issue in ESP-IDF where section attributes use __COUNTER__ macro, and this results in prototype and declaration having different sections assigned

This was previously fixed in the 8.x release.

lvgl#4391
lvgl#4404
…kept only on function declarations or static inline functions
@kisvegabor kisvegabor merged commit e3b747f into lvgl:master Jan 25, 2024
16 checks passed
@kisvegabor
Copy link
Member

Awesome, thank you!

How much performance improvement do you see when LV_ATTRIBUTE_FAST_MEM is used?

@ktand
Copy link
Contributor Author

ktand commented Jan 25, 2024

Awesome, thank you!

How much performance improvement do you see when LV_ATTRIBUTE_FAST_MEM is used?

I have not measured it. Will get back when I have some numbers.

@ktand ktand deleted the fix_lv_attribute_fast_mem branch January 25, 2024 19:12
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.

None yet

2 participants