public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libgcc: Add {unsigned ,}__int128 <-> _Decimal{32,64,128} conversion support [PR65833]
Date: Wed, 8 Nov 2023 18:07:17 +0000	[thread overview]
Message-ID: <5b701ac9-18c2-4c12-a530-b748e74d988d@codesourcery.com> (raw)
In-Reply-To: <ZUsw14bVvAyCni7X@tucnak>

On Wed, 8 Nov 2023, Jakub Jelinek wrote:

> Hi!
> 
> 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.
> 
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?

OK.

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2023-11-08 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  6:55 Jakub Jelinek
2023-11-08 18:07 ` Joseph Myers [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=5b701ac9-18c2-4c12-a530-b748e74d988d@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).