From: Derek M Jones <derek@knosof.co.uk>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [RFC] potential DR in handling of signed int and unholy mess in our and gcc implementations
Date: Thu, 19 Mar 2009 12:10:47 +0000 [thread overview]
Message-ID: <49C23647.5030209@knosof.co.uk> (raw)
In-Reply-To: <20090319013358.GZ28946@ZenIV.linux.org.uk>
Al,
> First of all, C99 has rather unpleasant inconsistency between
> 6.7.2p5 and footnote in 6.7.2.1p9. According to the former,
It is not really an inconsistency, one set of wording does not say
something about a particular case.
> However, the footnote in 6.7.2.1p9 says
> "As specified in 6.7.2 above, if the actual type specifier
> used is int or a typedef-name defined as int, then it is
> implementation-defined whether the bit-field is signed or unsigned."
Ok, so the wording in 7.6.2 does not mention the typedef case.
At most this is an editorial change to the Standard.
--
Derek M. Jones tel: +44 (0) 1252 520 667
Knowledge Software Ltd mailto:derek@knosof.co.uk
Source code analysis http://www.knosof.co.uk
prev parent reply other threads:[~2009-03-19 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 1:33 [RFC] potential DR in handling of signed int and unholy mess in our and gcc implementations Al Viro
2009-03-19 2:33 ` David Given
2009-03-19 12:10 ` Derek M Jones [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=49C23647.5030209@knosof.co.uk \
--to=derek@knosof.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 NNTP newsgroup(s).