https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #17 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Andreas Arnez from comment #16) > 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. I cannot force anyone to do anything, I was just pointing out what would be a good strategy to get the result that you want. > 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 Nobody will ever object to people fixing bugs ;) > #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?) Sure, I haven't looked at implications of both solutions in detail. The thing to remember is that the only people you need to convince are the MAINTAINERS of C FE. If you have never contributed to GCC, this may be useful: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps You may also send a WIP patch to gcc-patches@ and CC the C FE maintainers, just to get some early feedback.
