This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Deprecating cc0 (and consequently cc0 targets)
- From: John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>
- To: Jeff Law <law at redhat dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, Denis Chertykov <chertykov at gmail dot com>, hp at axis dot com, Andreas Schwab <schwab at linux-m68k dot org>, Matt Thomas <matt at 3am-software dot com>
- Date: Wed, 30 Oct 2019 09:29:40 +0100
- Subject: Re: Deprecating cc0 (and consequently cc0 targets)
- References: <61a6a83a-beec-24a2-7726-fba9e02f5ab9@physik.fu-berlin.de> <12e368c7-94db-1a42-6458-53596ebfb623@redhat.com>
Hi Jeff!!
On 10/29/19 8:34 PM, Jeff Law wrote:
>> 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'm not sure it'd be all that useful. The v850 bits would be a better
> starting point. The partial H8 transition isn't committed anywhere
> because it would certainly break the port.
I confused the H8 backend with the V850 backend, sorry for that. I have
realized later that the V850 backend is the one where the conversion
has been completed.
> I'll walk you through one example from the H8 port. This isn't complete
> enough to even test that it builds.
(...)
> This is where we describe (via the mode of the condition code register)
> what condition codes are set and how to extract them. These patterns
> can be added incrementally. But again, it's going to be a ton of work.
Thanks for the detailed explanation. I will be going through this over the
weekend trying to understand the details.
> My son is definitely still interested. But I doubt he'd likely be able
> to take up the task until the spring/summer of 2020. Additionally,
> there's some question of whether or not him doing the work could be
> viewed as a conflict of interest WRT the bug bounty because of his
> relationship to me.
I don't think there is a conflict of interest in any way. It's perfectly
fine to pick up the task yourself and receive the bounty. The community
doesn't really care who gets the job done.
And since I don't assume your employer is paying you to work on the m68k
backend, it's absolutely okay in my opinion to be paid for the task, time
isn't free, especially developer time.
It's very valuable to everyone in the various m68k communities to have
an up-to-date version of GCC available which is why so many people have
donated for the cause.
Thanks a lot for your time and input!
Adrian
--
.''`. 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