Skip to content
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

Fix operator precedence. #2730

Merged
merged 1 commit into from
Aug 28, 2017
Merged

Fix operator precedence. #2730

merged 1 commit into from
Aug 28, 2017

Conversation

vehre
Copy link
Contributor

@vehre vehre commented Aug 26, 2017

The precedence of [] is higher than *. I.e. *bitarray[i] means to first
deref by the index i and the pointer, but needed here is to first deref
the pointer and then the array.

@zbeekman
Copy link

This bug was discovered when enabling failed image support (part of the Fortran 2015 standard) in the OpenCoarrays project: sourceryinstitute/OpenCoarrays#439

The precedence of [] is higher than *. I.e. *bitarray[i] means to first
deref by the index i and the pointer, but needed here is to first deref
the pointer and then the array.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>
@raffenet raffenet merged commit 4d510cf into pmodels:master Aug 28, 2017
@raffenet
Copy link
Contributor

Looks good to me. Thanks!

@zbeekman
Copy link

Will this patch make it into the next release? Is there a target release date for the next stable release?

Cheers.

@zbeekman
Copy link

@ilovezfs @fxcoudert @MikeMcQuaid would a patch for this be accepted to the @Homebrew formula for MPICH until this makes it into the next release?

@fxcoudert
Copy link

fxcoudert commented Aug 28, 2017

@zbeekman We try to patch as little as possible, restricting ourselves to a) security fixes, b) build failures, c) high-impact bugs that affect a large fraction of our users.

I suggest you simply brew install mpich --HEAD

@zbeekman
Copy link

zbeekman commented Apr 3, 2018

@pmodels @raffenet It appears this hasn't made it into a release yet. Is it possible to backport? Should I open a PR against the 3.2.x branch?

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.

None yet

4 participants