https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #16 from Andreas Arnez <arnez at linux dot vnet.ibm.com> --- (In reply to Manuel López-Ibáñez from comment #15) > (In reply to Andreas Arnez from comment #11) > > Any news here? AFAIK the problem still exists. > > I still think the solution in comment #10 is the least invasive without > being a hack. But someone (you?) would need to submit a patch and get it > approved by the C maintainers. Well, I'm rather a GDB- than a GCC developer. My interest in this is to ensure that GDB doesn't become completely useless ;-) Also, I thought that David was a better candidate for fixing this because his patch introduced the regression. Anyway, if it helps speeding this up, and if nobody objects, I could give it a try. In this case I actually lean towards your suggestion from comment #13, to pass an explicit location to c_finish_loop. Somehow I don't like adding a function like c_parser_peek_token_keep_input_location and then using it only for this fix, just to get rid of it in the long run. (Right?)
