public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/110019] Reported line numbers ar off-by-1 when preprocessing source files Date: Sat, 29 Jul 2023 14:16:52 +0000 [thread overview] Message-ID: <bug-110019-4-yR9LKG5XBO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110019-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110019 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>: https://gcc.gnu.org/g:07c1033f003a858f4bfc6bb9e6b7ce67670db974 commit r13-7643-g07c1033f003a858f4bfc6bb9e6b7ce67670db974 Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Sat Jul 29 15:16:08 2023 +0100 PR modula2/110019 Reported line numbers off by 1 when cpp invoked. Fix off by one in m2.flex when the line number is set via cpp. gcc/m2/ChangeLog: PR modula2/110019 * gm2-compiler/SymbolKey.mod (SearchAndDo): Reformatted. (ForeachNodeDo): Reformatted. * gm2-compiler/SymbolTable.mod (AddListify): Join list with "," or "and" if more than one word is in the list. * m2.flex: Remove -1 from atoi(yytext) line number. gcc/testsuite/ChangeLog: PR modula2/110019 * gm2/cpp/fail/cpp-fail.exp: New test. * gm2/cpp/fail/foocpp.mod: New test. (cherry picked from commit 29c82c6ca929e0f5eccfe038dea71177d814c6b7) Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
prev parent reply other threads:[~2023-07-29 14:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-29 11:33 [Bug modula2/110019] New: " admin@tho-otto.de 2023-06-06 21:52 ` [Bug modula2/110019] " gaius at gcc dot gnu.org 2023-06-07 0:19 ` gaius at gcc dot gnu.org 2023-06-07 0:22 ` cvs-commit at gcc dot gnu.org 2023-06-07 0:23 ` gaius at gcc dot gnu.org 2023-07-29 14:16 ` cvs-commit at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110019-4-yR9LKG5XBO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).