public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/110759] [14 Regression] IEEE Fortran change broke RISC-V linux build
Date: Fri, 21 Jul 2023 05:30:53 +0000	[thread overview]
Message-ID: <bug-110759-4-uxMVoaJPHF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110759-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110759

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:f32518726ee8e836d12d49aec8432679fcc42503

commit r14-2695-gf32518726ee8e836d12d49aec8432679fcc42503
Author: Andrew Pinski <apinski@marvell.com>
Date:   Fri Jul 21 02:26:09 2023 +0000

    libfortran: Fix build for targets that don't have 10byte or 16 byte
floating point

    So the problem here is EXPAND_INTER_MACRO_16 expands to nothing if 16 byte
FP does not
    exist but we still add a comma after it and that causes a build failure.
    The same is true for EXPAND_INTER_MACRO_10 too.

    Committed as obvious after a bootstrap and test on x86_64-linux-gnu and
aarch64-linux-gnu.

    libgfortran/ChangeLog:

            PR libfortran/110759
            * ieee/ieee_arithmetic.F90
            (COMP_INTERFACE): Remove the comma after EXPAND_INTER_MACRO_16
            and EXPAND_INTER_MACRO_10.
            (EXPAND_INTER_MACRO_16): Add comma here if 16 byte fp exist.
            (EXPAND_INTER_MACRO_10): Likewise.

  parent reply	other threads:[~2023-07-21  5:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 22:15 [Bug libfortran/110759] New: " patrick at rivosinc dot com
2023-07-20 22:16 ` [Bug libfortran/110759] " patrick at rivosinc dot com
2023-07-20 22:18 ` [Bug libfortran/110759] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-20 22:19 ` pinskia at gcc dot gnu.org
2023-07-20 22:21 ` patrick at rivosinc dot com
2023-07-21  2:10 ` pinskia at gcc dot gnu.org
2023-07-21  2:19 ` patrick at rivosinc dot com
2023-07-21  2:24 ` pinskia at gcc dot gnu.org
2023-07-21  2:30 ` pinskia at gcc dot gnu.org
2023-07-21  2:31 ` patrick at rivosinc dot com
2023-07-21  5:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-21  5:31 ` pinskia at gcc dot gnu.org
2023-07-21  7:47 ` fxcoudert at gcc dot gnu.org

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=bug-110759-4-uxMVoaJPHF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).