[MIR] Support +inf and -inf literals - #221127
Conversation
|
Hello @Inconnu08 👋 Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this is your first PR, here are a few useful links covering our main contribution policies and review practices.
Please reply to this message to confirm that you have read these policies, especially the LLVM AI Tool Use Policy, and that any AI tool usage has been noted in the PR description. Frequently asked questionsHow do I add reviewers? This PR will be automatically labeled, and the relevant teams will be notified. For some parts of the project, reviewers may also be added automatically. You can also add reviewers manually using the Reviewers section on this page. If you cannot use that section, it is probably because you do not have write permissions for the repository. In that case, you can request a review by tagging reviewers in a comment using What if there are no comments? If you have not received any comments on your PR after a week, you can request a review by pinging the PR with a comment such as “Ping”. The common courtesy ping rate is once a week. Please remember that you are asking for volunteer time from other developers. Are any special GitHub settings required to contribute to LLVM? We only require contributors to have a public email address associated with their GitHub commits, see this section of LLVM Developer Policy for details. If you have questions, feel free to leave a comment on this PR, or ask on LLVM Discord or LLVM Discourse. Thank you, |
|
I've read the LLVM AI Tool Use Policy and the linked contribution policies. AI assistance has been disclosed in the PR description, and I've reviewed, tested, and understand the submitted changes. |
Support parsing
+infand-infas floating-point literals in MIR.The MIR lexer previously tokenized the leading sign separately, causing
G_FCONSTANT float +infandG_FCONSTANT float -infto fail with"expected a floating point literal".
Recognize signed infinity spellings as
FloatingPointLiteraltokens sothey can be handled by the existing floating-point constant parsing path.
Add a regression test covering both positive and negative infinity.
Fixes #221040
Assisted-by: ChatGPT (rubber ducking)