public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jirik.svoboda at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60846] New: Add 128-bit integer types for general use on 32-bit/64-bit CPUs Date: Tue, 15 Apr 2014 14:06:00 -0000 [thread overview] Message-ID: <bug-60846-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60846 Bug ID: 60846 Summary: Add 128-bit integer types for general use on 32-bit/64-bit CPUs Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jirik.svoboda at seznam dot cz (u)int64_t is available on all targets (32-bit and 64-bit) but __int128 isn't (according to http://gcc.gnu.org/onlinedocs/gcc/_005f_005fint128.html __int128 is only available if long long is 128-bits wide which doesn't seem to be the case for 32-bit/64-bit Intel targets). Please add something like (u)int128_t, i.e. 128-bit signed and unsigned integer types available on 32-bit and 64-bit compiler targets. This would allow, for example, representing an IPv6 address as a single scalar value. Address masking could be performed with a simple bitwise operator. Since 32-bit and 64-bit CPUs typically cannot operate on 128-bit integers directly, multiple instructions need to be generated for a single arithmetic operation.
next reply other threads:[~2014-04-15 14:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-15 14:06 jirik.svoboda at seznam dot cz [this message] 2014-04-15 14:11 ` [Bug c/60846] " rguenth at gcc dot gnu.org 2014-04-17 3:56 ` hp at gcc dot gnu.org 2014-04-17 3:58 ` hp at gcc dot gnu.org 2014-04-22 13:32 ` jirik.svoboda at seznam dot cz 2014-04-23 18:59 ` hp at gcc dot gnu.org 2020-03-26 1:13 ` mirh at protonmail dot ch 2020-03-27 21:10 ` feliks314159 at yahoo dot com 2020-03-27 22:09 ` pinskia at gcc dot gnu.org 2020-03-27 22:16 ` joseph at codesourcery dot com 2023-11-04 14:59 ` 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-60846-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).