On 26 January 2016 at 03:24, Manuel López-Ibáñez wrote:
> On 25 January 2016 at 20:17, Mikhail Maltsev wrote:
>> As I understand, the bug report suggests that we say "suggest || instead of |
>> when joining booleans" instead. We now have the API to show fix-it hints, so
>> it
>> would be nice to
On Mon, 2016-01-25 at 21:54 +, Manuel López-Ibáñez wrote:
> On 25 January 2016 at 20:17, Mikhail Maltsev wrote:
> > As I understand, the bug report suggests that we say "suggest || instead of
> > |
> > when joining booleans" instead. We now have the API to show fix-it hints,
> > so it
> > wo
On 25 January 2016 at 20:17, Mikhail Maltsev wrote:
> As I understand, the bug report suggests that we say "suggest || instead of |
> when joining booleans" instead. We now have the API to show fix-it hints, so
> it
> would be nice to output something like
>
> test.c:17:21: warning: suggest || in
On 26 January 2016 at 00:45, Prasad Ghangal wrote:
> Hi!
>
> I would like to solve "Bug 17896 - The expression (a>0 & b>0) should
> give clearer warning message (-Wparentheses)"
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17896) but I am new to
> gcc internals.
>
> Can someone please guide me
On 01/25/2016 10:15 PM, Prasad Ghangal wrote:
> Hi!
>
> I would like to solve "Bug 17896 - The expression (a>0 & b>0) should
> give clearer warning message (-Wparentheses)"
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17896) but I am new to
> gcc internals.
>
> Can someone please guide me how
