public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw@lug-owl.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56457] Bogus warning: loop-invariant.c:786:20: error: unused variable ‘regno’ when building vax-*-*
Date: Sat, 15 May 2021 11:30:51 +0000 [thread overview]
Message-ID: <bug-56457-4-M5U3ltbKKS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56457-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56457
Jan-Benedict Glaw <jbglaw@lug-owl.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbglaw@lug-owl.de
--- Comment #4 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
This can IMHO be closed. Using a 11.0.1 based compiler (Debian "unstable"'s
"gcc-snapshot package) to build current GCC versions (ie. tested with
5e0236d3b0e0d7ad98bcee36128433fa755b5558 as of May 9th, 2021), the warning
doesn't appear. Indeed, the VAX backend recently got quite a major overhault by
Maciej.
next prev parent reply other threads:[~2021-05-15 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 10:36 [Bug tree-optimization/56457] New: " amylaar at gcc dot gnu.org
2021-05-15 11:30 ` jbglaw@lug-owl.de [this message]
2024-03-17 20:57 ` [Bug tree-optimization/56457] " law 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-56457-4-M5U3ltbKKS@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).