Skip to content

[Fortran/gfortran] Disable bounds-check tests. #196

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

Merged
merged 2 commits into from
Jan 3, 2025

Conversation

vzakhari
Copy link
Contributor

@vzakhari vzakhari commented Jan 3, 2025

The tests started failing at -O2 after llvm/llvm-project#121544
Flang inlines hlfir.assign with hlfir.expr RHSs after the change,
so the runtime is not called, and it does not make the bounds checks.
Related feature request: Flang features to be implemented

The tests started failing at -O2 after llvm/llvm-project#121544
Flang inlines hlfir.assign with hlfir.expr RHSs after the change,
so the runtime is not called, and it does not make the bounds checks.
Related feature request: https://github.com/orgs/llvm/projects/12?pane=issue&itemId=29048733
@vzakhari vzakhari requested a review from tarunprabhu January 3, 2025 18:43
Copy link
Contributor

@tarunprabhu tarunprabhu left a comment

Choose a reason for hiding this comment

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

Will these tests ever pass in the future? In other words, as far as these tests are concerned, will flang's behavior always be different from gfortran? If so, could you add a comment clarifying this. It will help sort out which tests we can permanently disable.

@vzakhari
Copy link
Contributor Author

vzakhari commented Jan 3, 2025

Thank you for the review!

These tests will pass with -O0 as said in the comment. They will also pass whenever the bounds check feature is implemented.

@tarunprabhu
Copy link
Contributor

These tests will pass with -O0 as said in the comment. They will also pass whenever the bounds check feature is implemented.

Got it! I'm glad that that comment is still relevant. Thanks for the clarification.

@vzakhari vzakhari merged commit a5f02a8 into llvm:main Jan 3, 2025
1 check passed
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.

2 participants