On Mon, Jun 30, 2014 at 11:07:57PM +0200, Gerald Pfeifer wrote:
> On Mon, 30 Jun 2014, Jakub Jelinek wrote:
> > We don't have gcc-4.10/ directory, because the version of the next
> > release is still to be decided (hopefully at Cauldron next month).
>
> I'm a bit worried we'll miss entries in the
On Mon, Jun 30, 2014 at 08:16:01PM +, Joseph S. Myers wrote:
> On Mon, 30 Jun 2014, Marek Polacek wrote:
>
> > Basically everything I wrote in the patch for -Wincompatible-pointer-types
> > applies here as well. A new option, -Wint-conversion (to be compatible
> > with clang), is added to all
On Mon, 30 Jun 2014, Jakub Jelinek wrote:
> We don't have gcc-4.10/ directory, because the version of the next
> release is still to be decided (hopefully at Cauldron next month).
I'm a bit worried we'll miss entries in the meantime.
Can we use gcc-4.10/ for now and rename later if we go for
GCC
On Mon, Jun 30, 2014 at 10:51:59PM +0200, Gerald Pfeifer wrote:
> Can you please add this and the other one to gcc-4.10/changes.html?
>
> I can provide help if you need any.
We don't have gcc-4.10/ directory, because the version of the next release
is still to be decided (hopefully at Cauldron ne
Can you please add this and the other one to gcc-4.10/changes.html?
I can provide help if you need any.
Gerald
On Mon, 30 Jun 2014, Marek Polacek wrote:
> Basically everything I wrote in the patch for -Wincompatible-pointer-types
> applies here as well. A new option, -Wint-conversion (to be compatible
> with clang), is added to allow more fine-grained control over the warnings.
> I think we should print t
