public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/power-ieee128] fortran, libgfortran: Assorted -mabi=ieeelongdouble I/O fixes
Date: Tue,  4 Jan 2022 14:56:00 +0000 (GMT)	[thread overview]
Message-ID: <20220104145600.D93583858433@sourceware.org> (raw)

https://gcc.gnu.org/g:2319a9204f1c0b4a17753b9b66b086a5da38ede0

commit 2319a9204f1c0b4a17753b9b66b086a5da38ede0
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Jan 4 15:55:27 2022 +0100

    fortran, libgfortran: Assorted -mabi=ieeelongdouble I/O fixes
    
    Another patch, this fixes:
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -O0  execution test
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -O1  execution test
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -O2  execution test
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -O3 -g  execution test
    FAIL: gfortran.dg/intrinsic_spread_2.f90   -Os  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -O0  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -O1  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -O2  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -O3 -g  execution test
    FAIL: gfortran.dg/intrinsic_unpack_2.f90   -Os  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -O0  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -O1  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -O2  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -O3 -g  execution test
    FAIL: gfortran.dg/large_real_kind_form_io_1.f90   -Os  execution test
    FAIL: gfortran.dg/quad_2.f90   -O0  execution test
    FAIL: gfortran.dg/quad_2.f90   -O1  execution test
    FAIL: gfortran.dg/quad_2.f90   -O2  execution test
    FAIL: gfortran.dg/quad_2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
    FAIL: gfortran.dg/quad_2.f90   -O3 -g  execution test
    FAIL: gfortran.dg/quad_2.f90   -Os  execution test
    
    2022-01-04  Jakub Jelinek  <jakub@redhat.com>
    
    gcc/fortran/
            * trans-io.c (transfer_array_desc): Pass abi kind instead of kind
            to libgfortran.
    libgfortran/
            * io/read.c (convert_real): Add missing break; for the
            HAVE_GFC_REAL_17 case.

Diff:
---
 gcc/fortran/trans-io.c | 2 +-
 libgfortran/io/read.c  | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/fortran/trans-io.c b/gcc/fortran/trans-io.c
index e71075cb3fa..e122831c6f7 100644
--- a/gcc/fortran/trans-io.c
+++ b/gcc/fortran/trans-io.c
@@ -2528,7 +2528,7 @@ transfer_array_desc (gfc_se * se, gfc_typespec * ts, tree addr_expr)
   else
     charlen_arg = build_int_cst (gfc_charlen_type_node, 0);
 
-  kind_arg = build_int_cst (integer_type_node, ts->kind);
+  kind_arg = build_int_cst (integer_type_node, gfc_type_abi_kind (ts));
 
   tmp = gfc_build_addr_expr (NULL_TREE, dt_parm);
   if (last_dt == READ)
diff --git a/libgfortran/io/read.c b/libgfortran/io/read.c
index abc8cbe72d7..74c051422d2 100644
--- a/libgfortran/io/read.c
+++ b/libgfortran/io/read.c
@@ -203,6 +203,7 @@ convert_real (st_parameter_dt *dtp, void *dest, const char *buffer, int length)
 # else
       *((GFC_REAL_17*) dest) = __qmath_(strtoflt128) (buffer, &endptr);
 # endif
+      break;
 #endif
 
     default:


                 reply	other threads:[~2022-01-04 14:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220104145600.D93583858433@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).