On Tue, Jun 29, 2010 at 4:07 PM, Kevin Bowling <kevin.bowl...@kev009.com> wrote: > My argument is simply this, sorry if it wasn't clear in the last > email, bottom line up front: > - It can just as easily be removed in the future if it is broken for > more than one release rather than evicting support. > - It shouldn't add unwieldy maintenance overhead. The old stuff can > be walled off, conditionally built, and otherwise removed from the > main focus. > - The code is already written and just needs a maintainer. > - I have the hardware and desire to maintain it.
Actually the above does not describe what is going on with this code. This code is already "walled off" in how the back-end is allowed to do conditional support for it. It cannot be further walled off without creating a whole new target. So maybe creating a new target with the just RIOS support is needed. This will allow everyone to be happy and you can maintain the "new" target without burdening the progress of the rest of the rs6000 back-end. Thanks, Andrew Pinski
