From: Jeff Law <law@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Gunther Nikl <gnikl@justmail.de>,
Richard Sandiford <richard.sandiford@arm.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Denis Chertykov <chertykov@gmail.com>,
hp@axis.com, Andreas Schwab <schwab@linux-m68k.org>,
Matt Thomas <matt@3am-software.com>
Subject: Re: Deprecating cc0 (and consequently cc0 targets)
Date: Wed, 30 Oct 2019 18:10:00 -0000 [thread overview]
Message-ID: <f5d1f4aa-8e7f-8631-0051-21897f871542@redhat.com> (raw)
In-Reply-To: <b57cac86-1ee9-c6b1-0e9c-ad048a7e6fda@physik.fu-berlin.de>
On 10/30/19 11:57 AM, John Paul Adrian Glaubitz wrote:
> On 10/30/19 6:52 PM, Gunther Nikl wrote:
>> Richard Sandiford <richard.sandiford@arm.com> wrote:
>>> FWIW it's already possible to do the transform you mention with:
>>>
>>> s/(cc0)/(reg:CC CC_REGNUM_RC)/g
>>>
>>> (define_int_iterator CC_REGNUM_RC [(CC_REGNUM "reload_completed")])
>>
>> Since "reload_completed" is referenced, this is only about the CC0
>> conversion, right? Switching to LRA is not required for this step.
>
> I think it would be nice though that anyone who does the cc0 transition
> would also switch over to LRA unless that would be too much of a burden.
True, but the priority is the cc0 transition.
Jeff
next prev parent reply other threads:[~2019-10-30 18:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 15:38 Jeff Law
2019-09-20 17:22 ` Richard Biener
2019-09-20 17:45 ` Jeff Law
2019-09-21 20:48 ` Paul Koning
2019-09-21 21:04 ` Jeff Law
2019-09-21 23:48 ` Segher Boessenkool
2019-09-22 12:02 ` Richard Biener
2019-09-20 17:24 ` Joseph Myers
2019-09-22 10:45 ` coypu
2019-10-29 12:33 ` John Paul Adrian Glaubitz
2019-10-29 20:16 ` Jeff Law
2019-10-30 8:29 ` Richard Biener
2019-10-30 9:09 ` Richard Sandiford
2019-10-30 17:57 ` Gunther Nikl
2019-10-30 17:57 ` Jeff Law
2019-10-30 17:57 ` John Paul Adrian Glaubitz
2019-10-30 18:10 ` Jeff Law [this message]
2019-10-30 18:32 ` Jeff Law
2019-10-30 19:34 ` Paul Koning
2019-10-30 8:49 ` John Paul Adrian Glaubitz
2019-10-31 22:16 ` Segher Boessenkool
2020-01-27 14:35 ` Hans-Peter Nilsson
2020-01-27 18:23 ` Jeff Law
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=f5d1f4aa-8e7f-8631-0051-21897f871542@redhat.com \
--to=law@redhat.com \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gnikl@justmail.de \
--cc=hp@axis.com \
--cc=matt@3am-software.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=schwab@linux-m68k.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).