From: Diogo Sousa <diogogsousa@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: C99 Status - inttypes.h
Date: Fri, 22 Jul 2011 11:05:00 -0000 [thread overview]
Message-ID: <4E28BA8E.6090400@gmail.com> (raw)
In-Reply-To: <20110721174429.GB12907@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On 07/21/2011 06:44 PM, Joe Buck wrote:
> On Thu, Jul 21, 2011 at 07:30:16AM -0700, Joseph S. Myers wrote:
>> On Thu, 21 Jul 2011, Diogo Sousa wrote:
>>
>>> Hi,
>>>
>>> I checked the "library functions in <inttypes.h>" item in c99status
>>> (marked as "Library Issue") [http://gcc.gnu.org/c99status.html], and it
>>> seems that glibc implements everything the standard demands.
>>>
>>> Am I missing something or is this outdated? If so, where can I find more
>>> information about it?
>>
>> "Library Issue" simply means it's not GCC's resposibility; it says nothing
>> about the state in any particular library that may be used with GCC.
>
> But readers will focus on the word "Issue" here and think that there is
> something missing. Perhaps there should be a footnote explaining that
> glibc/eglibc has the needed support, but that other libraries might not.
>
I agree. It should say something as "Library Dependent", and report
glibc status.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-07-21 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 14:30 Diogo Sousa
2011-07-21 15:52 ` Joseph S. Myers
2011-07-21 18:13 ` Joe Buck
2011-07-22 11:05 ` Diogo Sousa [this message]
2011-07-22 13:03 ` Paulo J. Matos
2011-07-22 15:38 ` Joern Rennecke
2011-07-22 17:43 ` Paulo J. Matos
2011-07-22 20:12 ` James Dennett
2011-07-23 19:29 ` Weddington, Eric
2011-07-23 21:10 ` Eric Botcazou
2011-07-23 22:47 ` Weddington, Eric
2011-08-21 19:27 ` Gerald Pfeifer
2011-09-25 13:00 ` Joern Rennecke
2011-09-25 22:49 ` Joseph S. Myers
2011-09-25 22:53 ` Gerald Pfeifer
2011-09-26 7:11 ` Joseph S. Myers
2011-07-21 16:06 ` Basile Starynkevitch
2011-07-21 22:45 ` Ian Lance Taylor
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=4E28BA8E.6090400@gmail.com \
--to=diogogsousa@gmail.com \
--cc=gcc@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).