Skip to content

Comments

Add RInteger and RFloat to RVALUE#6723

Open
dearblue wants to merge 1 commit intomruby:masterfrom
dearblue:RVALUE
Open

Add RInteger and RFloat to RVALUE#6723
dearblue wants to merge 1 commit intomruby:masterfrom
dearblue:RVALUE

Conversation

@dearblue
Copy link
Contributor

Enhances detection of object size mismatches.


This patch reveals that 32-bit builds fail in AppVeyor.
This is because many 32-bit systems require 8-byte alignment for double and int64_t.

Enhances detection of object size mismatches.
@dearblue dearblue requested a review from matz as a code owner February 22, 2026 13:41
@github-actions github-actions bot added the core label Feb 22, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @dearblue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request improves the robustness of memory management by explicitly including RInteger and RFloat types within the RVALUE union. This modification is crucial for accurately detecting object size mismatches, particularly on 32-bit architectures where specific alignment requirements for data types like double and int64_t can lead to unexpected build failures.

Highlights

  • RVALUE Union Expansion: Added RInteger and RFloat members to the RVALUE union in src/gc.c under specific conditional compilation flags.
  • Improved Object Size Detection: This modification enhances the detection of object size mismatches, specifically addressing memory alignment requirements for double and int64_t on 32-bit systems.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/gc.c
    • Added RInteger and RFloat structs to the RVALUE union definition, guarded by conditional compilation directives.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds RInteger and RFloat to the RVALUE union under specific build configurations. This change ensures that the size and alignment requirements of these heap-allocated numeric types are considered when determining the size of RVALUE, which is used for object slots in GC heap pages. This helps in detecting object size and alignment mismatches at compile time, particularly on 32-bit systems, as noted in the description. The preprocessor conditions for including these structs appear to be correct and align with the configurations where RInteger and RFloat are actually used for heap allocations. The change is sound and improves the robustness of the memory layout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant