From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Jeff Law <law@redhat.com>
Cc: 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: Tue, 29 Oct 2019 12:33:00 -0000 [thread overview]
Message-ID: <61a6a83a-beec-24a2-7726-fba9e02f5ab9@physik.fu-berlin.de> (raw)
In-Reply-To: <1ee03bc0-ad1a-46dd-87bb-8288e990ce20@redhat.com>
Hello!
On September 20, 2019 5:38:38 PM GMT+02:00, Jeff Law <law@redhat.com> wrote:
>So this message is serving as official notice that we are *deprecating*
>all cc0 support in gcc-10. We are not removing any code or targets at
>this time -- removals would happen during the gcc-11 cycle.
>
>
>avr
>cris
>h8300
>m68k
>vax
>cr16
>
>This is based on actually looking at the backend patterns.
>backends.html indicates the mn103 port would be affected, but I think
>it's just out-of-date. Similarly it fails to mention cr16, but cr16
>clearly has affected patterns (I'll address that separately)
>
>This patch deprecates the affected targets. With some magic folks can
>continue to build them. However, if nobody steps forward to convert
>them from cc0 to MODE_CC those targets will be removed during the
>gcc-11
>cycle.
We have raised $5000 to support anyone willing to work on this for the
m68k target [1]. We really need the m68k to stay as it's essential to
be able to compile for Linux/m68k, NetBSD/m68k and AROS/m68k (a new
and ABI-compatible AmigaOS clone). I'm sure other communities like in the
NeXTStep, Atari and Mac/m68k forums are interested in keeping the backend
as well. I'm confident we will be able to raise even more money as the
community is large and active.
>If someone is interested in possibly doing a conversion, I would
>strongly recommend reviewing the best documentation we have on the
>subject:
>
>https://gcc.gnu.org/wiki/CC0Transition
>
>I worked with my son about a year ago to transition the v850 to MODE_CC
>using that page as a guideline. We also have a partial transition for
>the H8/300 port (not far enough to even build anything yet). I had
>hoped we would finish the H8/300 port last year and would have tackled
>another, but events have gotten in the way.
Any chance that the unfinished code can be shared? I'm looking for any
blueprints that can be used as a guidance for the work on the m68k
backend.
I have also created a guide on how to set up a QEMU virtual machine running
a fully fledged Debian/m68k which can be used for the development work [2].
>The transition isn't terribly hard, but does take time because of the
>number of patterns that have to be changed.
I have already looked at the conversion done on the V850 backend [3] but so far
I don't understand enough of the register representation stuff to be able
to know where to start. I'm seeing that all the "cc" attributes are being removed
but not replaced?
Adrian
> [1] https://www.bountysource.com/issues/80706251-m68k-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases
> [2] https://wiki.debian.org/M68k/QemuSystemM68k
> [3] https://github.com/gcc-mirror/gcc/commit/d6c5e987e730b3b2b9ff396d2361518ff9cb5e23
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2019-10-29 12:27 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 [this message]
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 ` John Paul Adrian Glaubitz
2019-10-30 18:10 ` Jeff Law
2019-10-30 17:57 ` Jeff Law
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=61a6a83a-beec-24a2-7726-fba9e02f5ab9@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=law@redhat.com \
--cc=matt@3am-software.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).