From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Fix minor CC0 removal fallout on cr16
Date: Fri, 21 May 2021 13:31:30 -0700 [thread overview]
Message-ID: <CAMe9rOpUhLWenZYrQPTXXc89raaOcsy_8Kf6MVK2Ejm95R4aug@mail.gmail.com> (raw)
In-Reply-To: <50cea1e6-88c5-26b8-04bf-a9da2071d5df@gmail.com>
On Wed, May 5, 2021 at 8:17 AM Jeff Law via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
>
> cr16 failed to build due to remnants of CC0 support (NOTICE_UPDATE_CC).
> This removes the macro and obvious bits necessary to support it.
> Committed to the trunk.
>
cr16-elf won't build:
/export/gnu/import/git/sources/gcc/gcc/config/cr16/cr16.md:797:16:
error: unknown rtx code `cc0'
/export/gnu/import/git/sources/gcc/gcc/config/cr16/cr16.md:797:19:
note: following context is `))]'
make[2]: *** [Makefile:2547: s-preds] Error 1
--
H.J.
prev parent reply other threads:[~2021-05-21 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 13:52 Jeff Law
2021-05-21 20:31 ` H.J. Lu [this message]
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=CAMe9rOpUhLWenZYrQPTXXc89raaOcsy_8Kf6MVK2Ejm95R4aug@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).