Skip to content

Conversation

@suetanvil
Copy link
Contributor

this fixes an issue where base can be out of range on a raspberry pi.

(This pull request cherry-picks the referenced commit onto the stable branch as requested in #6625 )

this fixes an issue where base can be out of range on a raspberry pi.
@suetanvil suetanvil requested a review from matz as a code owner September 18, 2025 16:42
@github-actions github-actions bot added the core label Sep 18, 2025
Copy link

@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.

Summary of Changes

Hello @suetanvil, 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 addresses a critical issue affecting BigInt operations on Raspberry Pi devices. It incorporates a targeted fix that resolves an 'out of range' error encountered during BigInt initialization, ensuring proper functionality and stability for applications utilizing BigInts on this platform. This change is a cherry-pick of an existing solution to the stable branch.

Highlights

  • BigInt Fix for Raspberry Pi: Corrected a type casting issue in mrb_bint_new_str within src/vm.c by explicitly casting s[1] to (int8_t), which resolves an "out of range" error when handling BigInts on Raspberry Pi devices.
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

@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 addresses a portability issue on platforms where char is unsigned by default, such as ARM architectures (e.g., Raspberry Pi). The change ensures that the base for a BigInt literal, which can be negative to indicate a negative number, is correctly interpreted as a signed value. By casting the character holding the base to int8_t, the code now behaves consistently across different architectures, preventing potential misinterpretation of the base value. The fix is correct, well-targeted, and improves the portability of the mruby interpreter.

@dearblue
Copy link
Contributor

@suetanvil
Is it intentional that the base branch is set to "master"?

If it is wrong, please try changing it to the "stable" branch.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request

@suetanvil suetanvil changed the base branch from master to stable September 20, 2025 03:48
@suetanvil
Copy link
Contributor Author

I have changed it (I hope). Sorry about that.

@matz matz merged commit 40436e4 into mruby:stable Sep 23, 2025
17 of 18 checks passed
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.

4 participants