public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args
Date: Tue, 02 Apr 2024 17:02:31 +0000	[thread overview]
Message-ID: <bug-114533-4-0JB3BIeSWY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114533-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Note also that in glibc, _Float128 support in printf code can only be used in
limited circumstances: either on powerpc64le, as one of the multiple supported
long double formats there, or through the sharing of the printf code with the
implementation of strfromf128.

In particular, there are no glibc printf formats corresponding directly to
_FloatN / _FloatNx types. There was support in principle at the WG14 meeting in
Strasbourg in January for having some form of printf/scanf support for such
types in C2y, but major work is still needed on the wording that was proposed
in N3184.

  parent reply	other threads:[~2024-04-02 17:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 12:48 [Bug libquadmath/114533] New: " doko at gcc dot gnu.org
2024-04-02 11:29 ` [Bug libquadmath/114533] " rguenth at gcc dot gnu.org
2024-04-02 11:45 ` jakub at gcc dot gnu.org
2024-04-02 12:04 ` schwab@linux-m68k.org
2024-04-02 12:36 ` fw at gcc dot gnu.org
2024-04-02 13:21 ` schwab@linux-m68k.org
2024-04-02 13:41 ` schwab@linux-m68k.org
2024-04-02 17:02 ` jsm28 at gcc dot gnu.org [this message]
2024-04-02 17:08 ` jakub at gcc dot gnu.org
2024-04-02 17:30 ` jvdelisle at gcc dot gnu.org
2024-04-02 17:34 ` jakub at gcc dot gnu.org
2024-04-02 18:26 ` doko at gcc dot gnu.org
2024-04-03  8:14 ` cvs-commit at gcc dot gnu.org
2024-04-21  4:08 ` cvs-commit at gcc dot gnu.org
2024-04-23  6:45 ` jakub 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-114533-4-0JB3BIeSWY@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).