On Thu, 23 Jan 2014, Marek Polacek wrote:
> shorten_compare can produce a better locinfo if we pass location
> from {,cp_}build_binary_op to it; op0/op1 there don't have location.
> Furthermore, I see no reason why use input_location in
> parser_build_binary_op when we can use more accurate location.
>
> I don't know if/how I can test the column info using dejagnu, so
> no testcase attached. But to give you an idea, instead of
The approach used is
/* { dg-warning "14:comparison is always false" } */
or similar, with the column number put at the start of the dg-error /
dg-warning text.
--
Joseph S. Myers
jos...@codesourcery.com
