kargl

Results 38 comments of kargl

You don't need to use openlibm on FreeBSD. FreeBSD's libm is already BE aware. In addition, most of openlibm is derived from FreeBSD's libm.

I've never used Darwin, so don't know. Looking at /usr/src/lib/msun/powerpc/fenv.h on FreeBSD shows the functions are declared as inline function and there is a lot of assembly. I suspect this...

Yep. Replacing `complx(knd), external :: f` with ``` interface function f(z) result(r) import knd complex(knd) r complex(knd), intent(in) :: z end function f end interface ``` removes the error message....

> You have to use `--implicit-interface` to support `external`. In the workaround you suggested, LFortran accepts provided interface and assumes that somewhere user will link concrete implementation with interface correctly....

> @kargl with #3929, the above code now behaves like this: > > ``` > )$ lfortran a.f90 --std=f23 > semantic error: Dummy argument 'm' not defined > --> a.f90:30:7...

Perhaps, `unit=42` is preconnected to a file named `fort.42`. 12.3.3.1 File access methods ... The method of accessing a file is determined when the file is connected to a unit...

Note, the half-cycle functions such as `sinpi(x) = sin(pi*x)` need to do an argument reduction step. I wrote the implementations in FreeBSD. Those have a 2-clause BSD license, so lfortran...

``` program foo use iso_fortran_env integer i do i = 1, 1 print *, real_kinds(i) end do end program foo ``` work/bin/lfortran -c a.f90 Segmentation fault (core dumped) I think...

A simple 'hello world' program works. % cat hello.f90 program hello print *, 'hello world' end program hello % work/bin/lfortran -o z hello.f90 && ./z hello world I'll peck at...

lfortran as of 2024-06-29 is broken on FreeBSD. % ../work/bin/lfortran -c mk_m90types.f90 Segmentation fault (core dumped) % gdb132 ../work/bin/lfortran (gdb) run mk_m90types.f90 Starting program: /usr/home/kargl/tmp/lfortran/work/bin/lfortran mk_m90types.f90 Program received signal SIGSEGV,...