On 7 May 2012 16:52, Paolo Carlini paolo.carl...@oracle.com wrote:
Hi,
On 06/11/2010 10:23 PM, Manuel López-Ibáñez wrote:
On 11 August 2009 02:01, Joseph S. Myersjos...@codesourcery.com wrote:
On Tue, 11 Aug 2009, Manuel López-Ibáñez wrote:
Modified the patch to make use of the new
Hi,
On 05/09/2012 02:54 PM, Manuel López-Ibáñez wrote:
On 7 May 2012 16:52, Paolo Carlinipaolo.carl...@oracle.com wrote:
Hi,
On 06/11/2010 10:23 PM, Manuel López-Ibáñez wrote:
On 11 August 2009 02:01, Joseph S. Myersjos...@codesourcery.comwrote:
On Tue, 11 Aug 2009, Manuel
On 9 May 2012 15:21, Paolo Carlini paolo.carl...@oracle.com wrote:
Good, I even have a patch essentially ready for that, but can you point me
to that detailed feedback? I couldn't find it when I looked for it.
This is how I understood the following paragraph:
I still think the warnings for
On Wed, 9 May 2012, Manuel López-Ibáñez wrote:
That is,
cases where you not are able to make a deduction about ranges = the
warnings are appropriate and should be disabled only under a separate
option.
cases where you are able to deduce the ranges = warning is not appropriate
Yes,
On 05/09/2012 03:54 PM, Joseph S. Myers wrote:
On Wed, 9 May 2012, Manuel López-Ibáñez wrote:
That is,
cases where you not are able to make a deduction about ranges = the
warnings are appropriate and should be disabled only under a separate
option.
cases where you are able to deduce the
Hi,
On 06/11/2010 10:23 PM, Manuel López-Ibáñez wrote:
On 11 August 2009 02:01, Joseph S. Myersjos...@codesourcery.com wrote:
On Tue, 11 Aug 2009, Manuel López-Ibáñez wrote:
Modified the patch to make use of the new c-c++-common testsuite.
Bootstrapped and regression tested on
