On 08/16/2018 10:49 AM, Joseph Myers wrote:
On Wed, 15 Aug 2018, Martin Sebor wrote:
Detecting some of these bugs without too much noise would require
moving the warning out of the front-end and to some later point
after VRP has run.
But you need the information about whether the conversion w
On Wed, 15 Aug 2018, Martin Sebor wrote:
> Detecting some of these bugs without too much noise would require
> moving the warning out of the front-end and to some later point
> after VRP has run.
But you need the information about whether the conversion was explicit or
implicit. If someone does
On 08/14/2018 05:53 AM, Martin Jambor wrote:
Hi,
when you try compiling a call to function abs and provide an unsigned
int in the argument in C++, you will get an error about ambiguous
overload. In C however, it will pass without silently. The following
patch adds a warning for these cases, be
On 8/14/18, Joseph Myers wrote:
> On Tue, 14 Aug 2018, Martin Jambor wrote:
>
>> when you try compiling a call to function abs and provide an unsigned
>> int in the argument in C++, you will get an error about ambiguous
>> overload. In C however, it will pass without silently. The following
>> p
On Tue, 14 Aug 2018, Martin Jambor wrote:
> when you try compiling a call to function abs and provide an unsigned
> int in the argument in C++, you will get an error about ambiguous
> overload. In C however, it will pass without silently. The following
> patch adds a warning for these cases, bec
Hi,
when you try compiling a call to function abs and provide an unsigned
int in the argument in C++, you will get an error about ambiguous
overload. In C however, it will pass without silently. The following
patch adds a warning for these cases, because I think it is likely that
such code does
