subject:"\[Bug debug\/67192\] Backward\-goto in loop can get wrong line number"

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-09-23 Thread manu at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 Manuel López-Ibáñez changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org,

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-09-22 Thread ppalka at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #12 from Patrick Palka --- (In reply to Manuel López-Ibáñez from comment #10) > (In reply to Manuel López-Ibáñez from comment #8) > > Does GCC work at all if input_location is saved and restored in > > c_parser_peek_token? I guess not

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-09-11 Thread arnez at linux dot vnet.ibm.com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #11 from Andreas Arnez --- Any news here? AFAIK the problem still exists.

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread manu at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #10 from Manuel López-Ibáñez --- (In reply to Manuel López-Ibáñez from comment #8) > Does GCC work at all if input_location is saved and restored in > c_parser_peek_token? I guess not, it seems too much still relies in > input_locatio

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread ppalka at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 Patrick Palka changed: What|Removed |Added CC||ppalka at gcc dot gnu.org --- Comment #9

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread manu at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Commen

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread arnez at linux dot vnet.ibm.com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #7 from Andreas Arnez --- (In reply to David Malcolm from comment #3) > The issue seems to be in here in c_parser_for_statement: > > warn_for_misleading_indentation (for_loc, body_loc, > c_parser_p

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread dmalcolm at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 David Malcolm changed: What|Removed |Added Attachment #36203|0 |1 is obsolete|

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread dmalcolm at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #5 from David Malcolm --- (In reply to David Malcolm from comment #3) > Created attachment 36203 [details] > Patch > > The issue seems to be in here in c_parser_for_statement: > > warn_for_misleading_indentation (for_loc, body_loc

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread dmalcolm at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #4 from David Malcolm --- Problem also affects while statements; reproduced using example from comment #0 w with "for (;;)" replaced with "while (1)"

[Bug debug/67192] Backward-goto in loop can get wrong line number

2015-08-18 Thread dmalcolm at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #3 from David Malcolm --- Created attachment 36203 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36203&action=edit Patch The issue seems to be in here in c_parser_for_statement: warn_for_misleading_indentation (for_loc, bod