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 libgcc/65833] Attempting to convert 128 bit integers to 128 bit decimal floating-point results in an unresolved symbol
Date: Thu, 09 Nov 2023 08:15:22 +0000	[thread overview]
Message-ID: <bug-65833-4-HkUt2WC5E6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65833-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

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

commit r14-5266-gf172b9d38db426d2b102c0f9c1fd58672acc6c9b
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Nov 9 09:14:07 2023 +0100

    libgcc: Add {unsigned ,}__int128 <-> _Decimal{32,64,128} conversion support
[PR65833]

    The following patch adds the missing
    {unsigned ,}__int128 <-> _Decimal{32,64,128}
    conversion support into libgcc.a on top of the _BitInt support
    (doing it without that would be larger amount of code and I hope all
    the targets which support __int128 will eventually support _BitInt,
    after all it is a required part of C23) and because it is in libgcc.a
    only, it doesn't hurt that much if it is added for some architectures
    only in GCC 15.
    Initially I thought about doing this on the compiler side, but doing
    it on the library side seems to be easier and more -Os friendly.
    The tests currently require bitint effective target, that can be
    removed when all the int128 targets support bitint.

    2023-11-09  Jakub Jelinek  <jakub@redhat.com>

            PR libgcc/65833
    libgcc/
            * config/t-softfp (softfp_bid_list): Add
            {U,}TItype <-> _Decimal{32,64,128} conversions.
            * soft-fp/floattisd.c: New file.
            * soft-fp/floattidd.c: New file.
            * soft-fp/floattitd.c: New file.
            * soft-fp/floatuntisd.c: New file.
            * soft-fp/floatuntidd.c: New file.
            * soft-fp/floatuntitd.c: New file.
            * soft-fp/fixsdti.c: New file.
            * soft-fp/fixddti.c: New file.
            * soft-fp/fixtdti.c: New file.
            * soft-fp/fixunssdti.c: New file.
            * soft-fp/fixunsddti.c: New file.
            * soft-fp/fixunstdti.c: New file.
    gcc/testsuite/
            * gcc.dg/dfp/int128-1.c: New test.
            * gcc.dg/dfp/int128-2.c: New test.
            * gcc.dg/dfp/int128-3.c: New test.
            * gcc.dg/dfp/int128-4.c: New test.

      parent reply	other threads:[~2023-11-09  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65833-4@http.gcc.gnu.org/bugzilla/>
2015-04-22  9:25 ` mpolacek at gcc dot gnu.org
2023-11-06 18:16 ` jakub at gcc dot gnu.org
2023-11-09  8:15 ` cvs-commit at gcc dot gnu.org [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=bug-65833-4-HkUt2WC5E6@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).