On 8/31/2012 3:32 PM, Joseph S. Myers wrote:
> My comments are:
>
> * TL;DR.
Then, perhaps, commenting is premature.
> * No specification given at the level of edits to C11.
That's correct. This is still an informal proposal.
> * At a glance, no or inadequate explanation of why library s
Snapshot gcc-4.6-20120831 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120831/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
My comments are:
* TL;DR.
* No specification given at the level of edits to C11.
* At a glance, no or inadequate explanation of why library solutions and
appropriate coding practices (such as the use of managed string libraries)
are inadequate.
* How does this compare to the array size checki
We have proposed an extension to C (primarily) and C++ (possibly)
to address buffer overflow prevention. Buffer overflows are still
a huge practical problem in C, and much important code is still
written in C. This is a new approach that may actually work.
The proposal,
"Safe arrays amd point
I have a question about GCC debug info. The tests
gcc.c-torture/compile/mipscop-[1234].c fail when compiled
with -g on MIPS (they are mips specific tests). This has
been reported in bugzilla as PR 54061.
The problem is:
register unsigned int cp0count asm ("$c0r1");
This is a coprocessor regist
.. let's add Jakub in CC, he knows those bits better than anyone else,
and I don't think they changed much lately anyway.
Paolo.
>>> GRAMMAR
>>>
>>> Support adding a second discriminator. This support is not for
>>> multiple inheritance, but for single inheritance when a second
>>> discriminator is used to further refine it. Look at struct
>>> tree_omp_clause. It contains a sub union. We can represent the
>>> hierarchy l
