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

On 03.12.21 10:28, Jakub Jelinek wrote: On Fri, Dec 03, 2021 at 08:29:53AM +0100, Thomas Koenig wrote: On 01.12.21 21:54, Jakub Jelinek via Fortran wrote: Inside of libgfortran, I think it should depend on some macro defined in libgfortran.h. #if defined(__powerpc64__) && __BYTE_ORDER__ ==

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

Hi Jakub, Note, we want to test both building gcc on ppc64le with older glibc and newer glibc (and that libgfortran will have the same ABI between both and one can move gcc including libgfortran and libquadmath from the older glibc setup to newer and make -mabi=ieeelongdouble work in Fortran t

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

Hi, I have loaded Advance Toolchain 15.0 on the system. It is located in /opt/at15.0. AT 15 provides a GCC 11.2 compiler and GLIBC 2.34. Thanks! I built a trunk compiler using the options: --enable-languages=c,c++,fortran \ --disable-plugin \ --enable-checking

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

On 04.12.21 07:39, Michael Meissner via Fortran wrote: I have loaded Advance Toolchain 15.0 on the system. It is located in /opt/at15.0. AT 15 provides a GCC 11.2 compiler and GLIBC 2.34. I tried bootstrapping (from a separate account I set up on the machine to make sure I don't mess up any

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

On 04.12.21 11:29, Jakub Jelinek wrote: If zlib devel isn't installed, drop --with-system-zlib option or use --without-system-zlib. You've asked in another mail how to configure gcc to default to -mabi=ieeelongdouble, that is --with-long-double-format=ieee Thanks for those hints. I have now m

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

On 04.12.21 17:12, Peter Bergner via Fortran wrote: As long as you keep the AT15 bin path before the system bin dirs, you should be fine. OK, what I have now is tkoenig@gcc-fortran:~$ echo $PATH /home/tkoenig/bin:/opt/at15.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/u

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

On 05.12.21 01:35, Peter Bergner wrote: Instead of setting LD_LIBRARY_PATH=/home/tkoenig/lib64 could you try setting it to LD_LIBRARY_PATH='$ORIGIN/lib64' instead? This would allow the other system binaries to not find your /home/tkoenig/lib64 directory so they'd behave normally. However, any

[patch, power-ieee128, committed] First stab at the library

Hi, here is a first stab at the library side of power-ieee128, committed to the branch. It compiles, but probably still has a lot of issues. It is also not called from the compiler yet. Regards Thomas 2021-10-19 Thomas Koenig Prepare library for REAL(KIND=17). This

Re: [PATCH] PR fortran/103610 - ICE in gfc_convert_mpz_to_signed, at fortran/simplify.c:193

Hi Harald, when simplifying SHAPE(), we rely on spec_dimen_size returning non-negative dimensions. That actually did not happen in all cases, as the testcase by Gerhard shows. (The testcase is rather fallout from the wrong simplification). The solution is trivial: simply check the dimensions

[patch, power-ieee128, committed] Fix pattern for _c17 and _r17

Pushed to the branch. With this patch, the instructions generated are the ones that are expected, for example: $ objdump --disassemble sum_r17.o | grep xsaddqp 3cc: 08 08 00 fc xsaddqp v0,v0,v1 3dc: 08 08 00 fc xsaddqp v0,v0,v1 3ec: 08 08 00 fc xsaddqp v0,v0,v1 410: 08

[pach, power-ieee128, committed] Generate config.h macros for ieee128 functions

Pushed to the branch. Generate config.h macros for IEEE128 math functions. libgfortran/ChangeLog: * acinclude.m4 (LIBGFOR_CHECK_MATH_IEEE128): New macro. * configure.ac: Use it. * config.h.in: Regenerate. * configure: Regenerate. diff --git a/libgfortran/Makefile

[power-ieee128] Which options for libquadmath / native ieee128

Hi, looking at what the REAL(KIND=17) numbers should be compiled for, I see the following options that should be considered: a) xsaddqp and friends are not supported by the CPU; libquadmath should be called for all operations, including simple arithmetic. b) xsaddqp and friends are support

Re: [PATCH] PR fortran/103718 & PR fortran/103719 - [11/12 Regression] ICE in doloop_contained_procedure_code

Hi Harald, there are several pretty obvious NULL pointer dereferences on valid and invalid code when checking do-loop contained stuff. Reported by Gerhard. Regtested on x86_64-pc-linux-gnu. OK for mainline/11-branch? OK for both. Thanks for cleaning this up! Regards Thomas

<    1   2   3