From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Evelina Dumitrescu <evelina_dumitrescu@yahoo.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: 128 bit integers support in gcc
Date: Thu, 23 Oct 2014 17:26:00 -0000 [thread overview]
Message-ID: <CAH6eHdThEZR=EderYHBRDKsVYUBAFDaXvEq+4RMhPgZ-0f=xyw@mail.gmail.com> (raw)
In-Reply-To: <1414056975.59023.YahooMailNeo@web160501.mail.bf1.yahoo.com>
On 23 October 2014 10:36, Evelina Dumitrescu wrote:
> Hi,
>
>
> I am working on a C/C++ networking project and I want to find an efficient way to store an IPv6 address. So far, I have thought on int128_t/uint128_t or __int128_t.
> I would like to know from which version of gcc are this types suported , for which platforms(especially IA-32/IA-64) and also if there are any known bugs.
See https://gcc.gnu.org/gcc-4.6/changes.html
"Support for a new data type __int128 for targets having wide enough
machine-mode support."
I don't know about known bugs, try searching bugzilla.
prev parent reply other threads:[~2014-10-23 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 9:36 Evelina Dumitrescu
2014-10-23 17:26 ` Jonathan Wakely [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='CAH6eHdThEZR=EderYHBRDKsVYUBAFDaXvEq+4RMhPgZ-0f=xyw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=evelina_dumitrescu@yahoo.com \
--cc=gcc-help@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).