public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.gustedt at inria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113887] New: no support for %w128 length modifiers Date: Mon, 12 Feb 2024 09:07:48 +0000 [thread overview] Message-ID: <bug-113887-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113887 Bug ID: 113887 Summary: no support for %w128 length modifiers Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jens.gustedt at inria dot fr Target Milestone: --- With C23 and the %w length modifiers and `_BitInt(128)` literals, it will finally be possible to have `[u]int128_t` types consistently as type aliases for all architectures where gcc defines the `__int128` types. I am currently implementing such a support on musl, but unfortunately the %w128 length modifiers are diagnosed as being wrong. ``` #include <stdio.h> int main() { unsigned __int128 x = 2; printf("%w128x\n", x); } ```
next reply other threads:[~2024-02-12 9:07 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-12 9:07 jens.gustedt at inria dot fr [this message] 2024-02-12 9:29 ` [Bug c/113887] " jakub at gcc dot gnu.org 2024-02-12 16:52 ` jsm28 at gcc dot gnu.org 2024-02-12 17:20 ` jens.gustedt at inria dot fr 2024-02-13 7:26 ` jens.gustedt at inria dot fr 2024-02-13 15:50 ` jsm28 at gcc dot gnu.org 2024-02-13 19:43 ` jens.gustedt at inria dot fr 2024-02-13 20:00 ` jens.gustedt at inria dot fr 2024-02-13 20:07 ` jakub at gcc dot gnu.org 2024-02-13 20:26 ` jens.gustedt at inria dot fr 2024-02-13 20:45 ` jakub at gcc dot gnu.org 2024-02-13 22:43 ` jsm28 at gcc dot gnu.org 2024-02-15 14:54 ` jens.gustedt at inria dot fr
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-113887-4@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: linkBe 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).