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/110003] Wrong source line listed for unused parameters Date: Sat, 29 Jul 2023 12:48:48 +0000 [thread overview] Message-ID: <bug-110003-4-Ctqb2eowZ8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110003-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110003 --- 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:6ace58a7241d500a9f57521a581d59f7a2f8b9fd commit r13-7641-g6ace58a7241d500a9f57521a581d59f7a2f8b9fd Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Sat Jul 29 13:48:22 2023 +0100 PR modula2/110003 Wrong source line listed for unused parameters Ensure that the parameter token position is recorded for both definition and implementation modules. The shadow variable is created inside BuildFormalParameterSection. The shadow variable needs to have the other definition or implementation module token position set when CheckFormalParameterSection is called. This allows the MetaError family of procedures to request the implementation module token position when reporting unused parameters. gcc/m2/ChangeLog: PR modula2/110003 * gm2-compiler/P2SymBuild.mod (GetParameterShadowVar): Import. (CheckFormalParameterSection): Call PutDeclared for the shadow variable associated with the parameter. (cherry picked from commit 7c0e2159afb3235950d3d8f61ef085cd1ccf0dfc) Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
prev parent reply other threads:[~2023-07-29 12:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-27 15:03 [Bug modula2/110003] New: " admin@tho-otto.de 2023-06-03 12:53 ` [Bug modula2/110003] " gaius at gcc dot gnu.org 2023-06-03 14:18 ` gaius at gcc dot gnu.org 2023-06-03 14:28 ` cvs-commit at gcc dot gnu.org 2023-06-03 14:29 ` gaius at gcc dot gnu.org 2023-07-29 12:48 ` 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-110003-4-Ctqb2eowZ8@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).