From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: Further limits/stdint issues
Date: Wed, 03 Dec 2014 11:38:03 +0100 [thread overview]
Message-ID: <1417603083.4936.1240.camel@eris.loria.fr> (raw)
In-Reply-To: <20141203010204.GA5440@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Am Dienstag, den 02.12.2014, 20:02 -0500 schrieb Rich Felker:
> UINT32_MAX and UINT64_MAX lack the U suffix. This probably does not
> matter for UINT64_MAX since the value does not fit in intmax_t, but
> for UINT32_MAX, it will be treated as a signed value at the
> preprocessor level without the U suffix.
right, so I should add such a signed/unsigned preprocessor test to my
test program. (makes it even more ugly)
> It may be possible to eliminate the #if UINTPTR_MAX == UINT64_MAX
> check for defining INT64_C() etc. using an expression that yields the
> right type naturally (e.g. (c)+0*0x7fffffffffffffff etc.) but I'm not
> sure if that's an improvement.
With the patch I proposed, there is no conditional compilation of that
kind anymore.
Jens
--
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536 ::
:: :::::::::::::::::::::: gsm France : +33 651400183 ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-12-03 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 1:02 Rich Felker
2014-12-03 4:10 ` Glenn Weinberg
2014-12-03 5:03 ` Rich Felker
2014-12-03 16:34 ` Glenn Weinberg
2014-12-03 17:01 ` Rich Felker
2014-12-03 21:08 ` Glenn Weinberg
2014-12-03 10:38 ` Jens Gustedt [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=1417603083.4936.1240.camel@eris.loria.fr \
--to=jens.gustedt@inria.fr \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).