This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: --std vs __intN
- From: Marc Glisse <marc dot glisse at inria dot fr>
- To: DJ Delorie <dj at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Sat, 7 Jun 2014 00:19:05 +0200 (CEST)
- Subject: Re: --std vs __intN
- Authentication-results: sourceware.org; auth=none
- References: <201406060116 dot s561GQwY005060 at greed dot delorie dot com> <alpine dot DEB dot 2 dot 10 dot 1406060738220 dot 2168 at laptop-mg dot saclay dot inria dot fr> <201406061825 dot s56IPERL028941 at greed dot delorie dot com> <alpine dot DEB dot 2 dot 10 dot 1406062146280 dot 5945 at laptop-mg dot saclay dot inria dot fr> <201406062034 dot s56KYHVQ017207 at greed dot delorie dot com>
On Fri, 6 Jun 2014, DJ Delorie wrote:
The USE macro may not be needed, making them equivalent to
defined(MACRO_GIVING_THE_TYPE) seems good enough to me.
I was following the USE_INT128 macro style from before.
Ah, ok.
The other macros provide type, bitsize, min, max, and umax.
Seems like a lot. Since gcc only supports 2's complement, min is -max-1
for signed type and 0 for unsigned, it doesn't need a macro. Etc. But I
agree that's a detail.
In my opinion, we don't need to preserve that __STRICT_ANSI__ behavior.
That implies testsuite changes though...
Yes. That's my point, it may be better to change a couple minor things in
the testsuite instead of making something too complicated in the library.
--
Marc Glisse