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/110126] Variables are reported as unused when only referenced by ASM statements
Date: Mon, 12 Jun 2023 14:26:54 +0000	[thread overview]
Message-ID: <bug-110126-4-Otrl90dJYU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110126-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110126

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>:

https://gcc.gnu.org/g:bf470895905e9152424076d1630a9d2c60de023b

commit r14-1718-gbf470895905e9152424076d1630a9d2c60de023b
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date:   Mon Jun 12 15:25:39 2023 +0100

    PR modula2/110126 variables are reported as unused when referenced by ASM
fix

    This patch fixes the trash list of the asm statement.  It introduces a
    separate build procedure for trashed elements.

    gcc/m2/ChangeLog:

            PR modula2/110126
            * gm2-compiler/M2Quads.def (BuildAsmElement): Remove
            trash parameter.
            (BuildAsmTrash): New procedure.
            * gm2-compiler/M2Quads.mod (BuildAsmTrash): New procedure.
            (BuildAsmElement): Remove trash parameter.
            * gm2-compiler/P3Build.bnf (AsmTrashList): Rewrite.

    Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>

  parent reply	other threads:[~2023-06-12 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 12:45 [Bug modula2/110126] New: " admin@tho-otto.de
2023-06-06 14:26 ` [Bug modula2/110126] " gaius at gcc dot gnu.org
2023-06-07  5:06 ` admin@tho-otto.de
2023-06-07 12:50 ` gaius at gcc dot gnu.org
2023-06-08 20:33 ` gaius at gcc dot gnu.org
2023-06-08 23:56 ` cvs-commit at gcc dot gnu.org
2023-06-08 23:56 ` gaius at gcc dot gnu.org
2023-06-09  6:21 ` admin@tho-otto.de
2023-06-09  7:19 ` admin@tho-otto.de
2023-06-12 12:26 ` gaius at gcc dot gnu.org
2023-06-12 13:35 ` admin@tho-otto.de
2023-06-12 14:26 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-12 14:28 ` gaius at gcc dot gnu.org
2023-06-13 11:36 ` admin@tho-otto.de
2023-07-11 18:13 ` admin@tho-otto.de
2023-07-29 16:25 ` cvs-commit at gcc dot gnu.org
2023-07-29 20:04 ` cvs-commit at gcc dot gnu.org
2023-07-29 20:13 ` gaius at gcc dot gnu.org

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-110126-4-Otrl90dJYU@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: link
Be 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).