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 bootstrap/107299] [13 regression] ICE in stage 1 after  r13-3307-g8efc38347a7444
Date: Mon, 06 Mar 2023 22:42:04 +0000	[thread overview]
Message-ID: <bug-107299-4-9LFyw1EgSi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107299-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Michael Meissner <meissner@gcc.gnu.org>:

https://gcc.gnu.org/g:306c7b1ac3e4413288e6930b00a3cab2133c4e57

commit r13-6507-g306c7b1ac3e4413288e6930b00a3cab2133c4e57
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Mon Mar 6 17:38:33 2023 -0500

    PR target/107299: Fix build issue when long double is IEEE 128-bit

    This patch updates the IEEE 128-bit types used in libgcc.

    At the moment, we cannot build GCC when the target uses IEEE 128-bit long
    doubles, such as building the compiler for a native Fedora 36 system.  The
    build dies when it is trying to build the _mulkc3.c and _divkc3 modules.

    This patch changes libgcc to use long double for the IEEE 128-bit base type
if
    long double is IEEE 128-bit, and it uses _Float128 otherwise.  The built-in
    functions are adjusted to be the correct version based on the IEEE 128-bit
base
    type used.

    While it is desirable to ultimately have __float128 and _Float128 use the
same
    internal type and mode within GCC, at present if you use the option
    -mabi=ieeelongdouble, the __float128 type will use the long double type and
not
    the _Float128 type.  We get an internal compiler error if we combine the
    signbitf128 built-in with a long double type.

    I've gone through several iterations of trying to fix this within GCC, and
    there are various problems that have come up.  I developed this alternative
    patch that changes libgcc so that it does not tickle the issue.  I hope we
can
    fix the compiler at some point, but right now, this is preventing people on
    Fedora 36 systems from building compilers where the default long double is
IEEE
    128-bit.

    2023-03-06   Michael Meissner  <meissner@linux.ibm.com>

    libgcc/

            PR target/107299
            * config/rs6000/_divkc3.c (COPYSIGN): Use the correct built-in
based on
            whether long double is IBM or IEEE.
            (INFINITY): Likewise.
            (FABS): Likewise.
            * config/rs6000/_mulkc3.c (COPYSIGN): Likewise.
            (INFINITY): Likewise.
            * config/rs6000/quad-float128.h (TF): Remove definition.
            (TFtype): Define to be long double or _Float128.
            (TCtype): Define to be _Complex long double or _Complex _Float128.
            * libgcc2.h (TFtype): Allow machine config files to override this.
            (TCtype): Likewise.
            * soft-fp/quad.h (TFtype): Likewise.

  parent reply	other threads:[~2023-03-06 22:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 21:16 [Bug other/107299] New: [13 regression] seurer at gcc dot gnu.org
2022-10-18  5:43 ` [Bug bootstrap/107299] [13 regression] ICE in stage 1 after r13-3307-g8efc38347a7444 aldyh at gcc dot gnu.org
2022-10-18  5:52 ` linkw at gcc dot gnu.org
2022-10-18  7:01 ` aldyh at gcc dot gnu.org
2022-10-18  7:08 ` aldyh at gcc dot gnu.org
2022-10-18  7:26 ` rguenth at gcc dot gnu.org
2022-10-18  7:27 ` rguenth at gcc dot gnu.org
2022-10-18  7:27 ` rguenth at gcc dot gnu.org
2022-10-18 10:13 ` aldyh at gcc dot gnu.org
2022-10-18 10:16 ` aldyh at gcc dot gnu.org
2022-10-26 17:46 ` seurer at gcc dot gnu.org
2023-03-06 22:42 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-09 15:10 ` redi at gcc dot gnu.org
2023-03-15  9:40 ` rguenth 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-107299-4-9LFyw1EgSi@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).