From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Eric Botcazou <botcazou@adacore.com>, gcc-patches@gcc.gnu.org
Subject: Re: H8 cc0 conversion
Date: Fri, 4 Dec 2020 16:03:34 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2012041508230.656242@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2011251650360.9890@arjuna.pair.com>
On Wed, 25 Nov 2020, Hans-Peter Nilsson wrote:
> Current cc0 head-count is down to avr, cr16, h8300, vax, with
> two of them recently having patches posted, alas not a lot of
> ports left to try this advice.
Hmm, the VAX port surely did not qualify for an innovative approach
anyway (though still I made it a bit different by means of how I (ab)used
subst iterators and chose to ignore both rtx's in SELECT_CC_MODE; arguably
that was the only sustainable choice) as it has been too bitrotten to make
experiments with without a major cleanup being made first, and by the time
I started the effort no time has left for it. Otherwise you would simply
not know if any phenomenon observed is due to the change being made or
unrelated breakage.
As usually with software however nothing has been cast in stone (even
things made to be as stable as ABIs do change from time to time), so with
the conversion out of the way any remaining cleanup can be made and then
we can try removing the splits in favour to clobbers exposed pre-reload
and see what happens. If that turns out feasible, then other ports of
this kind may follow.
You may want to have your observations posted in the wiki however.
Maciej
next prev parent reply other threads:[~2020-12-04 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 19:27 Jeff Law
2020-11-24 4:49 ` Hans-Peter Nilsson
2020-11-24 5:50 ` Jeff Law
2020-11-24 10:02 ` Hans-Peter Nilsson
2020-11-24 11:08 ` Eric Botcazou
2020-11-24 15:23 ` Jeff Law
2020-11-25 22:05 ` Hans-Peter Nilsson
2020-11-28 18:44 ` Paul Koning
2020-12-04 16:03 ` Maciej W. Rozycki [this message]
2020-12-08 5:43 ` Maciej W. Rozycki
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=alpine.LFD.2.21.2012041508230.656242@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.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).