Uh oh!
There was an error while loading. Please reload this page.
Move MonoClass:inlinearray_value out of MonoClass - #109363
Conversation
syfFerdinand
commented
Oct 30, 2024
@dotnet-policy-service agree |
lambdageek
commented
Oct 31, 2024
Thanks for the contribution @syfFerdinand ! |
lambdageek
commented
Oct 31, 2024
/cc @steveisok |
Uh oh!
There was an error while loading. Please reload this page.
…into fix/move-inlinearray-value
…alue for PROP_INLINEARRAY_VALUE
steveisok
commented
Nov 8, 2024
@kg can you please give this a review? |
Uh oh!
There was an error while loading. Please reload this page.
syfFerdinand
commented
Nov 13, 2024
Hi @kg and @steveisok, |
kg
commented
Nov 13, 2024
I've never dealt with this problem before, but it appears that if you download each of the offsets artifacts I linked to, it will be a ZIP file with updated versions of the .h files in it. You would then check in these new .h files to update the offsets. I don't think you want to manually edit the offsets. |
steveisok
commented
Nov 13, 2024
Unless I'm completely mistaken, we don't auto-generate the offsets any longer and they need to be updated in tree. @akoeplinger is that correct? |
We generate them in PR builds so you can just download and check in the updated offsets, like @kg mentioned. This is the message on the build, let me know if I can make it clearer:
edit I just noticed that the name of the artifacts in the message is not right, it's |
To match the message in the build log, see #109363 (comment)
syfFerdinand
commented
Nov 13, 2024
Thank you all for your assistance and guidance throughout this process. I have updated the offset files with the latest versions from the build artifacts and committed the changes. Is there anything else that needs to be corrected or adjusted? |
kg
commented
Nov 13, 2024
Once the necessary tests pass I think we should be good. I'll keep an eye on it. |
To match the message in the build log, see #109363 (comment)
syfFerdinand
commented
Nov 25, 2024
kg
commented
Nov 25, 2024
Out of memory issues on the wasm lanes are common, so I don't think the librarytests lane failure indicates a bug you created. |
kg
commented
Nov 25, 2024
Thank you for your contribution! |
To match the message in the build log, see dotnet#109363 (comment)
* Moved inlinearray_value to infrequent_data structure in MonoClass * Move MonoClass:inlinearray_value out of MonoClass, setting explicit value for PROP_INLINEARRAY_VALUE * Mark mono_class_get_inlinearray_value with MONO_COMPONENT_API for proper export * Remove obsolete offset for inlinearray_value in MonoClass * Update Mono offset files with latest versions from build artifacts
Summary
This PR addresses issue #103913 by moving the inlinearray_value property from MonoClass to the infrequent_data structure. This change aims to optimize memory usage by storing rarely used properties in a less frequently accessed structure.
Details
inlinearray_valuefromMonoClasstoMonoPropertyBagwithin theinfrequent_datastructure.inlinearray_valueaccess to use the new structure.Related Issue
Fixes#103913