From: DJ Delorie <dj@redhat.com>
To: libstdc++@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] change specific int128 -> generic intN
Date: Fri, 09 May 2014 18:29:00 -0000 [thread overview]
Message-ID: <201405091829.s49ITEIU015189@greed.delorie.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1405090907070.3684@laptop-mg.saclay.inria.fr> (message from Marc Glisse on Fri, 9 May 2014 09:59:29 +0200 (CEST))
> Well, it wasn't a hard requirement, it is just that the library has
> to use a more complicated way to get the precision (use (unsigned
> TYPE)(-1) to get the unsigned max and compute the precision from
> that, probably).
We could define macros for the precision too, and we already know max
and min values as macros, it's "just a matter of" exporting that info
to the C++ headers somehow.
> > Would it be acceptable for the compiler to always define a set of
> > macros for each of the intN types?
>
> What set of macros do you have in mind?
In general, I meant. They'd be predefined for pretty much every
compile, not just the C++ headers.
next prev parent reply other threads:[~2014-05-09 18:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 23:03 DJ Delorie
2014-04-15 5:54 ` Marc Glisse
2014-04-15 6:17 ` DJ Delorie
2014-04-17 20:17 ` Marc Glisse
2014-05-08 23:34 ` DJ Delorie
2014-05-09 0:26 ` Marc Glisse
2014-05-09 2:21 ` DJ Delorie
2014-05-09 7:59 ` Marc Glisse
2014-05-09 18:29 ` DJ Delorie [this message]
2014-06-21 16:24 ` DJ Delorie
2014-06-21 17:35 ` Marc Glisse
2014-06-24 5:40 ` DJ Delorie
2014-06-28 10:09 ` Marc Glisse
2014-06-21 20:17 ` Joseph S. Myers
2014-06-24 5:51 ` DJ Delorie
2014-06-24 23:32 ` [patch 1/4] " DJ Delorie
2014-06-27 11:22 ` Eric Botcazou
2014-06-27 21:04 ` DJ Delorie
2014-06-27 21:38 ` Joseph S. Myers
2014-06-27 21:50 ` DJ Delorie
2014-06-27 21:57 ` Joseph S. Myers
2014-06-27 23:31 ` DJ Delorie
2014-07-01 2:23 ` DJ Delorie
2014-07-02 8:18 ` Eric Botcazou
2014-07-02 14:57 ` DJ Delorie
2014-07-03 15:53 ` Eric Botcazou
2014-07-03 16:12 ` DJ Delorie
2014-07-03 16:30 ` Bernd Schmidt
2014-07-03 20:01 ` DJ Delorie
2014-07-04 9:50 ` Eric Botcazou
2014-07-04 9:45 ` Eric Botcazou
2014-07-07 6:01 ` DJ Delorie
2014-07-10 8:32 ` Eric Botcazou
2014-07-10 16:35 ` DJ Delorie
2014-07-11 9:06 ` Eric Botcazou
2014-07-11 16:31 ` DJ Delorie
2014-07-12 9:15 ` Eric Botcazou
2014-06-24 23:38 ` [patch 2/4] " DJ Delorie
2014-06-24 23:39 ` [patch 3/4] " DJ Delorie
2014-06-24 23:42 ` [patch 4/4] " DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2014-04-14 23:01 [patch] " DJ Delorie
2014-05-01 22:15 ` Joseph S. Myers
2014-05-01 23:35 ` DJ Delorie
2014-05-02 17:45 ` Joseph S. Myers
2014-05-04 21:09 ` DJ Delorie
2014-05-05 18:58 ` Mike Stump
2014-05-05 19:01 ` DJ Delorie
2014-05-07 16:44 ` Joseph S. Myers
2014-05-08 3:08 ` DJ Delorie
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=201405091829.s49ITEIU015189@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).