public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113887] no support for %w128 length modifiers Date: Tue, 13 Feb 2024 20:45:02 +0000 [thread overview] Message-ID: <bug-113887-4-0a08RWUT6m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113887-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113887 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- #if 42 == ((__int128) +42wb) && -35 == ((__int128) +-35wb) #else #warning warn #endif works with both gcc and clang if __BITINT_MAXWIDTH__ >= 128. That said, for UINT128_C it would need to use __uint128_t rather than unsigned __int128, as the latter doesn't work in preprocessor expressions, as that is interpreted as ((0 0) +42wb) then.
next prev parent reply other threads:[~2024-02-13 20:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-12 9:07 [Bug c/113887] New: " jens.gustedt at inria dot fr 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 [this message] 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-0a08RWUT6m@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).