On Mon, 26 Sep 2011, Gerald Pfeifer wrote:
> Joseph, how do you suggest to rephrase the note on activation?
> Just -std=c99 as an option to GCC which then triggers the appropriate
> #defines?
Yes.
--
Joseph S. Myers
jos...@codesourcery.com
On Sun, 25 Sep 2011, Joern Rennecke wrote:
> Attached.
Thanks, Jörn!
! "Library Issue" means that support may or may not be available depending
! on the C library used; for example, the GNU C library supports all C99
I suggest a full stop isntead of ";" before "for example" and to just
say "defi
On Sun, 25 Sep 2011, Joern Rennecke wrote:
> ! "Library Issue" means that support may or may not be available depending
> ! on the C library used; for example, the GNU C library supports all C99
> ! features, provided _ISOC99_SOURCE and/or _GNU_SOURCE is defined in the
> ! source code or with a -D
Quoting Gerald Pfeifer :
On Fri, 22 Jul 2011, Joern Rennecke wrote:
I agree that trying to track every library there would be a maintenance
burden, but giving one example of a library that works is meaningful.
And, since GCC is still a GNU project, mentioning the status of GNU libc
doesn't seem
On Fri, 22 Jul 2011, Joern Rennecke wrote:
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 sa
> -Original Message-
> From: Eric Botcazou [mailto:ebotca...@adacore.com]
> Sent: Saturday, July 23, 2011 1:28 PM
> To: Weddington, Eric
> Cc: gcc@gcc.gnu.org; Joern Rennecke; Paulo J. Matos
> Subject: Re: C99 Status - inttypes.h
>
> > Realistically, how man
> Realistically, how many unique libraries are used for all of the GCC
> targets? I would think that it has to be some low, finite number.
There is at least one per OS (Linux, Solaris, HP-UX, IRIX, Tru64, *BSD, VMS,
Windows, etc) plus variants depending on the version of the OS.
--
Eric Botcazo
> -Original Message-
> From: Joern Rennecke [mailto:amyl...@spamcop.net]
> Sent: Friday, July 22, 2011 9:22 AM
> To: Paulo J. Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: C99 Status - inttypes.h
>
> I agree that trying to track every library there would be a m
On Fri, Jul 22, 2011 at 8:37 AM, Paulo J. Matos wrote:
> On 22/07/11 16:22, Joern Rennecke wrote:
>>>
>>> I have to disagree, library issue means that it's an issue with the
>>> library, not gcc.
>>
>> It still makes sense to clarify the language to indicate that, depending
>> on
>> the library us
On 22/07/11 16:22, Joern Rennecke wrote:
I have to disagree, library issue means that it's an issue with the
library, not gcc.
It still makes sense to clarify the language to indicate that, depending on
the library used, this might be, in fact, a library non-issue.
We might be interpreting t
Quoting "Paulo J. Matos" :
On 22/07/11 00:47, Diogo Sousa wrote:
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. I
On 22/07/11 00:47, Diogo Sousa wrote:
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 "Li
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 " item in c99status
>>> (marked as "Library Issue") [http://gcc.gnu.org/c99status.html], and i
Basile Starynkevitch writes:
> This brings another question. Can a GCC pass use intptr_t (the standard int
> of the same
> size as a void* pointer)? This is quite useful, for instance when one wants
> to compute an
> hash, or a unique sorted rank (to be used inside B-trees) from the address of
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 " item in c99status
> > (marked as "Library Issue") [http://gcc.gnu.org/c99status.html], and it
> > seems that glibc implements everythi
On Thu, 21 Jul 2011 15:24:00 +0100
Diogo Sousa wrote:
> I checked the "library functions in " 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 outdate
On Thu, 21 Jul 2011, Diogo Sousa wrote:
> Hi,
>
> I checked the "library functions in " 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
Hi,
I checked the "library functions in " 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?
Thank yo
18 matches
Mail list logo
