Snapshot gcc-5-20141005 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20141005/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On 5 October 2014 20:29, Ali Abdul Ghani wrote:
> gcc Became very bad
Unsubstantiated nonsense that has nothing to do with the thread you're
replying to.
> gcc Became the slower and more errors
If you have evidence for this please report it to bugzilla with code
to reproduce the problem.
gcc Became very bad
gcc Became the slower and more errors
Because WeChange Implementation to c++
I hope to return to c Implementation
2014-10-05 12:10 جرينتش-07:00, Manuel López-Ibáñez :
> Dear GCC users,
>
> As you may have noticed, GCC diagnostics have steadily improved in
> recent releases. In
Dear GCC users,
As you may have noticed, GCC diagnostics have steadily improved in
recent releases. In addition to the myriad of bugs fixed per release,
every release had at least one major improvement in diagnostics.
Unfortunately, the number of people contributing to this effort is
very limited
On 5 October 2014 03:39, Adrian May wrote:
> But it absolutely has to follow the preprocessor, so how do I do that?
> I'm a bit surprised about that being a problem cos when I look at
> preprocessor output it looks very convenient - I get one big file but
> it's full of clues as to where it all ca
