This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] config.gcc: Obsolete c4x.


Zack Weinberg wrote:
Mark Mitchell <mark@codesourcery.com> writes:


Ralf Corsepius wrote:


I will also certainly say that if there is consensus that we should
resurrect this port, then we should do so. I'm not stubbornly
about killing it. A possible compromise would be to bring it back
on the 4.0 branch only, and see if anyone fixes it before 4.1.

Sounds like a reasonable (may-be temporary) compromise to me, esp. because the c4x had been in 4.0.0, removing it for 4.0.1 doesn't make much sense to me.

Does anyone besides Ralf have an opinion on this proposal?


I think it makes more sense to have it only on mainline than only on
4.0 branch.  We generally prefer repairs like the one c4x needs, to be
conducted on mainline and then backported to release branches.  If we
leave it on the branch and take it out on mainline

Well, that's the normal case when we remove a target: we remove it from mainline for the next release, but it's still lingering (albeit, perhaps, in more-working form than C4x) on the previous release branch. So, I'm not sure if there's a reason to do something different here.


Kazu, let's make Ralf and Joel happy, and make this a somewhat more gentle transition. Would you please add the bits back to the 4.0 branch? At the same time, add c4x to the list of obsolete targets, so that --enable-obsolete is required to actually build it. Let's leave the mainline alone; if someone actually does come forward to maintain the port, we can resurrect it.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]