public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore
Date: Thu, 28 May 2020 18:42:01 +0000	[thread overview]
Message-ID: <bug-95252-4-UGBouck7kv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95252-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jim Wilson <wilson at gcc dot gnu.org> ---
I've got 3 new g++ testsuite failures.  So we might still need an exact list of
USEs.  I hadn't thought about RVE.  That will have to be checked also. 
RV32/RV64 shouldn't matter, as the mode in the USEs doesn't matter.  Unless
maybe you want to use a multi-word load to match multiple registers with a
single USE to reduce the size of the patterns, in which case it would need to
be different for rv32 and rv64.  If we do need an exact list of USEs, maybe we
can use a match_parallel to simplify the patterns.

  parent reply	other threads:[~2020-05-28 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  6:51 [Bug target/95252] New: " bina2374 at gmail dot com
2020-05-25 21:59 ` [Bug target/95252] " wilson at gcc dot gnu.org
2020-05-27  5:06 ` kito at gcc dot gnu.org
2020-05-27 23:18 ` wilson at gcc dot gnu.org
2020-05-27 23:19 ` wilson at gcc dot gnu.org
2020-05-27 23:20 ` wilson at gcc dot gnu.org
2020-05-28  3:39 ` kito at gcc dot gnu.org
2020-05-28 18:42 ` wilson at gcc dot gnu.org [this message]
2020-06-01 16:04 ` kito.cheng at gmail dot com
2020-06-03  3:32 ` kito at gcc dot gnu.org
2020-06-12  3:37 ` kito 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-95252-4-UGBouck7kv@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).