public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "admin@tho-otto.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/110126] New: Variables are reported as unused when only referenced by ASM statements Date: Mon, 05 Jun 2023 12:45:23 +0000 [thread overview] Message-ID: <bug-110126-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110126 Bug ID: 110126 Summary: Variables are reported as unused when only referenced by ASM statements Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: admin@tho-otto.de Target Milestone: --- In the following fragment: MODULE foo; VAR x: INTEGER; PROCEDURE test; BEGIN ASM("" : : "m"(x)); END test; END foo. x is reported as unused (same happens when specifying it as output parameter) Even worse, when used as input operand only, the whole asm statement seems to be optimized away.
next reply other threads:[~2023-06-05 12:45 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-05 12:45 admin@tho-otto.de [this message] 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 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@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).