BUG,MAINT: f2py doesn't map iso_c_binding values by default
#24553
Labels
Comments
f2py doesn't map iso_c_binding values by default
HaoZeke
added a commit
to HaoZeke/numpy
that referenced
this issue
Aug 26, 2023
charris
pushed a commit
to charris/numpy
that referenced
this issue
Sep 2, 2023
charris
pushed a commit
to charris/numpy
that referenced
this issue
Nov 11, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Reproducer
Consider:
! isoc_oddity.f90 module coddity use iso_c_binding, only: c_double implicit none contains subroutine c_add(a, b, c) bind(c, name="c_add") real(c_double), intent(in) :: a, b real(c_double), intent(out) :: c print*, "a is", a print*, "b is", b c = a + b end subroutine c_add end module coddityWhich compiles fine but doesn't do what one might expect:
python -m numpy.f2py -c isoc_oddity.f90 -m buggy python -c 'import buggy;res=buggy.coddity.c_add(1, 2); print(f"res: {res}, exp: 3, eq: {res==3}")' a is 2.0000004731118679 b is 5.3049894774131808E-315 res: 1.0, exp: 3, eq: FalseClearly,
c_doubleis not being interpreted correctly. This has an easy user-land fix though, adding an.f2py_f2cmapfile to the directory (or passing a named file in via the command line) with the following:Will work correctly:
python -m numpy.f2py -c isoc_oddity.f90 -m buggy --f2cmap isoc_f2cmap python -c 'import buggy;res=buggy.coddity.c_add(1, 2); print(f"res: {res}, exp: 3, eq: {res==3}")' a is 1.0000000000000000 b is 2.0000000000000000 res: 3.0, exp: 3, eq: TrueSuggestion
This is definitely unexpected behavior,
iso_c_bindingvalues should be mapped correctly by default, or atleast loaded in when theiso_c_bindingmodule is used.The text was updated successfully, but these errors were encountered: