public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX <fxcoudert@gmail.com>
To: Fortran <fortran@gcc.gnu.org>
Cc: Mikael Morin <morin-mikael@orange.fr>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran: add IEEE_MODES_TYPE, IEEE_GET_MODES and IEEE_SET_MODES
Date: Wed, 21 Sep 2022 10:07:50 +0200	[thread overview]
Message-ID: <8DAE36B3-8C8D-4BD3-83B6-6E5E3034B049@gmail.com> (raw)
In-Reply-To: <E799B15C-0575-442D-848D-69FDB389EF87@gmail.com>

I forgot to include the gfortran.map part of the patch, and so the test failed on platforms that have symbol versioning.
Fix below committed to master.

FX



commit ce8aed75a38b468490ecab4c318e3eb08d468608 (HEAD -> master)
Author: Francois-Xavier Coudert <fxcoudert@gmail.com>
Date:   2022-09-21 10:04:22 +0200

    Fortran: add symbols in version map for IEEE_GET_MODES and IEEE_SET_MODES
    
    The symbols were forgotten in the patch that added IEEE_GET_MODES
    and IEEE_SET_MODES.
    
    2022-09-21  Francois-Xavier Coudert  <fxcoudert@gcc.gnu.org>
    
    libgfortran/
    
            * gfortran.map: Add symbols for IEEE_GET_MODES
            and IEEE_SET_MODES.

diff --git a/libgfortran/gfortran.map b/libgfortran/gfortran.map
index e0e795c3d48..db9b86cb183 100644
--- a/libgfortran/gfortran.map
+++ b/libgfortran/gfortran.map
@@ -1759,3 +1759,9 @@ GFORTRAN_12 {
   _gfortran_transfer_real128_write;
 #endif
 } GFORTRAN_10.2;
+
+GFORTRAN_13 {
+  global:
+    __ieee_exceptions_MOD_ieee_get_modes;
+    __ieee_exceptions_MOD_ieee_set_modes;
+} GFORTRAN_12;


      reply	other threads:[~2022-09-21  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 16:30 FX
2022-09-10 16:54 ` FX
2022-09-17 12:14 ` Mikael Morin
2022-09-19 12:25   ` FX
2022-09-21  8:07     ` FX [this message]

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=8DAE36B3-8C8D-4BD3-83B6-6E5E3034B049@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=morin-mikael@orange.fr \
    /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).