public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Claudiu Zissulescu <claziss@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3521] arc: Update ZOL pattern. Date: Tue, 14 Sep 2021 09:28:09 +0000 (GMT) [thread overview] Message-ID: <20210914092809.2D2433858424@sourceware.org> (raw) https://gcc.gnu.org/g:9bb20299ba1d1cc3bbd83a07a777fcc5a93cfeb0 commit r12-3521-g9bb20299ba1d1cc3bbd83a07a777fcc5a93cfeb0 Author: Claudiu Zissulescu <claziss@synopsys.com> Date: Tue Sep 14 12:25:43 2021 +0300 arc: Update ZOL pattern. The ZOL pattern is missing modes which may lead to errors during var_tracking. Add them. gcc/ * config/arc/arc.md (doloop_end): Add missing mode. (loop_end): Likewise. Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com> Diff: --- gcc/config/arc/arc.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gcc/config/arc/arc.md b/gcc/config/arc/arc.md index 90ba85e274e..4919d275820 100644 --- a/gcc/config/arc/arc.md +++ b/gcc/config/arc/arc.md @@ -4966,8 +4966,8 @@ core_3, archs4x, archs4xd, archs4xd_slow" (const_int 1)) (label_ref (match_operand 1 "" "")) (pc))) - (set (match_dup 0) (plus (match_dup 0) (const_int -1))) - (unspec [(const_int 0)] UNSPEC_ARC_LP) + (set (match_dup 0) (plus:SI (match_dup 0) (const_int -1))) + (unspec:SI [(const_int 0)] UNSPEC_ARC_LP) (clobber (match_dup 2))])] "" { @@ -4996,8 +4996,8 @@ core_3, archs4x, archs4xd, archs4xd_slow" (const_int 1)) (label_ref (match_operand 1 "" "")) (pc))) - (set (match_dup 0) (plus (match_dup 0) (const_int -1))) - (unspec [(const_int 0)] UNSPEC_ARC_LP) + (set (match_dup 0) (plus:SI (match_dup 0) (const_int -1))) + (unspec:SI [(const_int 0)] UNSPEC_ARC_LP) (clobber (match_scratch:SI 2 "=X,&r"))] "" "@
reply other threads:[~2021-09-14 9:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210914092809.2D2433858424@sourceware.org \ --to=claziss@gcc.gnu.org \ --cc=gcc-cvs@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).