Re: [power-ieee128] What should the math functions be annotated with?

2021-12-01 Thread Jakub Jelinek via Fortran
On Wed, Dec 01, 2021 at 09:54:50PM +0100, Jakub Jelinek wrote: > sinl in C when compiled with -mabi=ieeelongdouble), but I'm not sure > if those need to be declared by libgfortran or math.h declares them). To answer this myself, just tried on Fedora 34 and we'd need to declare those ourselves. Bec

Re: [power-ieee128] What should the math functions be annotated with?

2021-12-01 Thread Jakub Jelinek via Fortran
On Wed, Dec 01, 2021 at 09:34:47PM +0100, Thomas Koenig via Gcc wrote: > I am currently working on implementing the IEEE 128-bit floating > on POWER. One of the things to decide is what to call the > math functions for the library calls. > > Example: libgfortran/generated/bessel_r16.c currently h

[power-ieee128] What should the math functions be annotated with?

2021-12-01 Thread Thomas Koenig via Fortran
I am currently working on implementing the IEEE 128-bit floating on POWER. One of the things to decide is what to call the math functions for the library calls. Example: libgfortran/generated/bessel_r16.c currently has #if defined(GFC_REAL_16_IS_FLOAT128) #define MATHFUNC(funcname) funcname ##

Re: [PATCH, PR90030] Fortran OpenMP/OpenACC array mapping alignment fix

2021-12-01 Thread Jakub Jelinek via Fortran
On Thu, Nov 04, 2021 at 04:23:43PM +0800, Chung-Lin Tang wrote: > 2021-11-04 Chung-Lin Tang > Thomas Schwinge > > PR fortran/90030 > > gcc/fortran/ChangeLog: > > * trans-openmp.c (gfc_omp_finish_clause): Remove fold_convert to pointer > to char_type_node, add gcc_