From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: [PATCH 3/4] use exact types for the [U]INTXX_C macros
Date: Wed, 03 Dec 2014 11:20:04 +0100 [thread overview]
Message-ID: <1417602004.4936.1233.camel@eris.loria.fr> (raw)
In-Reply-To: <20141203000132.GA4574@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Am Dienstag, den 02.12.2014, 19:01 -0500 schrieb Rich Felker:
> On Tue, Dec 02, 2014 at 10:37:54PM +0100, Jens Gustedt wrote:
> > These are DR 209 and 456
> >
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_209.htm
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1892.htm#dr_456
>
> I don't see where your interpretation is clear from these. DR 209
> added the text I cited. It's not clear what the change made to
> 7.18.4.1 is (I don't have the old text in front of me) so perhaps you
> could shed some light on why you think it requires the odd types.
I also only have the corrected version in front, but I vaguely
remember that the change was from types [u]intXX_t to [u]int_leastXX_t
because the macros are supposed to exist, even if the corresponding
[u]intXX_t doesn't.
> DR 456 just seems to state that DR 209 already adequately handled the
> situation and that no further change is needed.
exactly, furthermore they add
The committee believes that DR209 is still appropriate in that
"compiler magic" must be used for the implementation of these
macros. The committee does not consider this a defect.
The part about the compiler magic is completely senseless when
supposing that the constants promote.
In addition, from discussion on the WG14 mailing list I see that
people there expect the macros to resolve to the unpromoted type when
used in _Generic.
And isn't all of this just the purpose of these macros? If we'd
suppose they promote, standard literals to denote the constants would
mainly suffice: they already do the right thing for narrow types,
namely promotion.
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 --]
next prev parent reply other threads:[~2014-12-03 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 14:50 Jens Gustedt
2014-12-02 18:03 ` Rich Felker
2014-12-02 19:20 ` Jens Gustedt
2014-12-02 19:44 ` Rich Felker
2014-12-02 21:37 ` Jens Gustedt
2014-12-03 0:01 ` Rich Felker
2014-12-03 10:20 ` Jens Gustedt [this message]
2014-12-03 13:21 ` Szabolcs Nagy
2014-12-03 14:17 ` Jens Gustedt
2014-12-03 14:50 ` Rich Felker
2014-12-03 14:47 ` Rich Felker
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=1417602004.4936.1233.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).