From: Jeff Law <jeffreyalaw@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [committed] Trivial bfin-elf fix
Date: Tue, 4 May 2021 08:58:32 -0600 [thread overview]
Message-ID: <93c67f29-8d9d-523d-46f9-66878f050176@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 84 bytes --]
Whee, no more cc0! This fixes trivial fallout. Installed on the trunk.
Jeff
[-- Attachment #2: bfin.patch --]
[-- Type: text/plain, Size: 708 bytes --]
commit b50ccaf6dd743c373af95e90935b9a2b72157f3a
Author: Jeff Law <jlaw@tachyum.com>
Date: Tue May 4 08:56:28 2021 -0600
Make bfin-elf build again
gcc/
* config/bfin/bfin.h (NOTICE_UPDATE_CC): Remove.
diff --git a/gcc/config/bfin/bfin.h b/gcc/config/bfin/bfin.h
index f282d05d43d..823ca2d7124 100644
--- a/gcc/config/bfin/bfin.h
+++ b/gcc/config/bfin/bfin.h
@@ -786,8 +786,6 @@ typedef struct {
|| GET_CODE (X) == LABEL_REF \
|| (GET_CODE (X) == CONST && symbolic_reference_mentioned_p (X)))
-#define NOTICE_UPDATE_CC(EXPR, INSN) 0
-
/* Max number of bytes we can move from memory to memory
in one reasonably fast instruction. */
#define MOVE_MAX UNITS_PER_WORD
reply other threads:[~2021-05-04 14:58 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=93c67f29-8d9d-523d-46f9-66878f050176@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).