From: Thomas Koenig <tkoenig@netcologne.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Michael Meissner <meissner@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Peter Bergner <bergner@linux.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [power-ieee128] fortran, libgfortran: Add remaining missing *_r17 symbols
Date: Tue, 4 Jan 2022 21:16:45 +0100 [thread overview]
Message-ID: <7ecbaadf-95ff-4265-a487-e9938d4f6d67@netcologne.de> (raw)
In-Reply-To: <20220104172856.GH2646553@tucnak>
Hi Jakub,
> Following patch adds remaining missing *_r17 entrypoints, so that
> we have 91 *_r16 and 91 *_r17 entrypoints (and 24 *_c16 and 24 *_c17).
>
> This fixes:
> FAIL: gfortran.dg/dec_math.f90 -O0 execution test
> FAIL: gfortran.dg/dec_math.f90 -O1 execution test
> FAIL: gfortran.dg/dec_math.f90 -O2 execution test
> FAIL: gfortran.dg/dec_math.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
> FAIL: gfortran.dg/dec_math.f90 -O3 -g execution test
> FAIL: gfortran.dg/dec_math.f90 -Os execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -O0 execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -O1 execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -O2 execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/ieee/dec_math_1.f90 -Os execution test
>
> Ok for power-ieee128?
Looks good to me.
Thanks!
Thomas
next prev parent reply other threads:[~2022-01-04 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 14:23 [power-ieee128] fortran, libgfortran: Assorted -mabi=ieeelongdouble I/O fixes Jakub Jelinek
2022-01-04 14:36 ` Thomas Koenig
2022-01-04 17:28 ` [power-ieee128] fortran, libgfortran: Add remaining missing *_r17 symbols Jakub Jelinek
2022-01-04 20:16 ` Thomas Koenig [this message]
2022-01-04 18:08 ` [power-ieee128] fortran, libgfortran: Assorted -mabi=ieeelongdouble I/O fixes Jakub Jelinek
2022-01-04 20:38 ` Thomas Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ecbaadf-95ff-4265-a487-e9938d4f6d67@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).